> 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/customer.md).

# Customer

Read and maintain the Mimeeq account associated with your API key. This is your account-level identity and configuration, rather than a company or a contact stored inside the account.

Use this section to read account settings before synchronizing contact details, supported languages, currencies, markets, or public price-list groups. These settings provide reference values used by other API resources.

### What you can do

| Task                      | Reference                                                                                          |
| ------------------------- | -------------------------------------------------------------------------------------------------- |
| Find available customer   | [List Customer](https://help.mimeeq.com/developers/customer/list-customer)                         |
| Change customer contact   | [Update Customer Contact](https://help.mimeeq.com/developers/customer/update-customer-contact)     |
| Change customer languages | [Update Customer Languages](https://help.mimeeq.com/developers/customer/update-customer-languages) |
| Change customer pricing   | [Update Customer Pricing](https://help.mimeeq.com/developers/customer/update-customer-pricing)     |

### Before you start

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

### Important behaviour

Read the current customer first. Contact, language and pricing updates replace their respective submitted settings; send the complete values you intend to keep. Exactly one language and one currency must be the default. Theme values are returned for reference; these endpoints do not edit the theme or upload a logo.


---

# 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/customer.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.