> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/api/contacts.md).

# Contacts

Manage people associated with companies in your Mimeeq account. A contact is a business record; creating one does not create a Tier 1 account user or send an invitation.

Use this section to synchronize names, email addresses, contact details and reporting relationships from a CRM. Contact detail also exposes invitation and portal-user assignment state where available.

### What you can do

| Task                    | Reference                                                                    |
| ----------------------- | ---------------------------------------------------------------------------- |
| Find available contacts | [List Contacts](https://help.mimeeq.com/developers/contacts/list-contacts)   |
| Add a new contact       | [Create Contact](https://help.mimeeq.com/developers/contacts/create-contact) |
| Read one contact        | [Get Contact](https://help.mimeeq.com/developers/contacts/get-contact)       |
| Change contact          | [Update Contact](https://help.mimeeq.com/developers/contacts/update-contact) |

### Before you start

Your API key needs `contacts:read` to read these resources. Use `contacts:write` for write operations.

### Important behaviour

Create the company first and use its `companyId`. A reporting manager must be another contact in the same company. Updates replace submitted fields and arrays; changing a contact’s company can be rejected when it has quotations, an invitation or a portal user. Use Users, Invitations and Roles for Tier 1 account access.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.mimeeq.com/api/contacts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.