> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/mailchimp.md).

# Mailchimp

## OAuth app properties

| Property                | Value                                                                                                                 |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** Any Mailchimp user can authorize one app.                                                                    |
| **Vendor review**       | **None.** A listing in the Mailchimp Marketplace is optional.                                                         |
| **Review time**         | Not applicable.                                                                                                       |
| **Users before review** | No limit.                                                                                                             |
| **App owner**           | Any Mailchimp account.                                                                                                |
| **Regions**             | One app for all accounts. The connector reads each account's data center (`dc`) from the OAuth metadata.              |
| **Client secret**       | No expiry documented. Shown once; it can be rotated, after which requests signed with the old secret fail with `401`. |
| **Rate limits**         | 10 simultaneous connections per Mailchimp user; calls time out after 120 seconds. No volume limit.                    |
| **Checked**             | 2026-11-13                                                                                                            |

**Limitations**

* The access token does not expire. It stops working when the user revokes the app or is removed from the Mailchimp account; the user then connects again.
* The 10 simultaneous connections are shared with every other integration of the same user. Above that Mailchimp answers `429`, and the limit cannot be raised.
* After you rotate the client secret, update `clientSecret` in the Backoffice, otherwise new connections fail.

Sources: [OAuth 2](https://mailchimp.com/developer/marketing/api-concepts/authentication/oauth-2), [Set up an OAuth app](https://mailchimp.com/developer/marketing/guides/access-user-data-oauth-2/), [Rate limits and timeouts](https://mailchimp.com/developer/marketing/api-concepts/rate-limits-and-timeouts). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

### **Setup Mailchimp account**

Sign up with Mailchimp: <https://mailchimp.com/>

### **2. Register OAuth app**

Now you need to add an OAuth application. Navigate to: Profile > Extras > Registered apps.

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-7fb02f0ffe7a8d807ca992a96c6c3b66326b185e%2Fmailchimp-1.png?alt=media" alt=""><figcaption><p>Navigate to Profile</p></figcaption></figure>

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-1f00a085e5db9937b1d00655e52c2f78d64254b4%2Fmailchimp-2.png?alt=media" alt=""><figcaption><p>Navigate to Registered apps</p></figcaption></figure>

Click on the "Register an app" button.

#### Specify client details

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-6e2607ef036c50a694fd1f86fd71eb6d768d9b4a%2Fmailchimp-3.png?alt=media" alt=""><figcaption><p>Specify app details</p></figcaption></figure>

#### Generate client secret

Now save the OAuth client and copy the client ID and secret. You will need them later.

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-d1b5b304ce523e312ab538c83b6a58f494d3507a%2Fmailchimp-4.png?alt=media" alt=""><figcaption><p>Copy Client ID and Client secret</p></figcaption></figure>

## Backoffice configuration

Configuration ID: `appmixer:mailchimp` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — Client ID of the Mailchimp app registered above. Not needed when Mailchimp is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Client secret of the same app. Not needed with the Auth Hub.
* `outputFilePrefix` — Optional. File name prefix of the CSV file that **ListCampaigns**, **ListFiles** and **ListMembers** create when their output is set to a file; the file is named `<prefix>-<component id>.csv`. Default `mailchimp-export`.

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-685c76027e3f4d5be459506b08c343be769d3d12%2Fmailchimp-5.png?alt=media" alt=""><figcaption><p>Backoffice Mailchimp connector configuration</p></figcaption></figure>

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:mailchimp -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>"
}'
```


---

# 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://docs.appmixer.com/connector-configuration/mailchimp.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.
