Mailchimp
Mailchimp is a comprehensive marketing automation platform that enables businesses to create, manage, and optimize email marketing campaigns, manage subscriber lists, track campaign performance, and automate customer engagement workflows to drive business growth.
Power end-to-end data operations for your Mailchimp API with Nexla. Our bi-directional Mailchimp connector is purpose-built for Mailchimp, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Mailchimp or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Mailchimp workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a Mailchimp credential, you need to obtain your API key and identify your data center from your Mailchimp account. Mailchimp uses API key authentication with Basic Authentication, where the API key is used as the password and any string can be used as the username.
To obtain your Mailchimp API credentials, follow these steps:
-
Sign in to your Mailchimp account using your administrator credentials.
-
Click on your account name or profile icon in the top right corner of the Mailchimp dashboard.
-
Select Account from the dropdown menu, then click Extras > API keys in the account settings.
-
If you don't have an API key yet, scroll down to the Your API keys section and click Create A Key to generate a new API key.
-
Enter a name for your API key (e.g., "Nexla Integration") to help you identify it later.
-
Click Generate Key to create the API key. The API key will be displayed immediately after generation.
-
Copy the API key immediately and store it securely, as you will need it to configure your Nexla credential. The API key may not be accessible again after you navigate away from the page.
-
To identify your data center, look at the URL when you're logged into your Mailchimp account. The data center is the subdomain in your account URL (e.g., if your URL is
https://us1.admin.mailchimp.com, your data center isus1). Common data centers includeus1,us2,us3,us4,us5,us6,us7,us8,us9,us10,us11,us12,us13,us14,us15,us16,us17,us18,us19,us20,us21,eu1,eu2,eu3,eu4,eu5,eu6,eu7,eu8,eu9,eu10,eu11,eu12,eu13,eu14,eu15,eu16,eu17,eu18,eu19,eu20,eu21,ap1,ap2,ap3,ap4,ap5,ap6,ap7,ap8,ap9,ap10,ap11,ap12,ap13,ap14,ap15,ap16,ap17,ap18,ap19,ap20,ap21.
The API key is used with Basic Authentication for all API requests to the Mailchimp API. The data center is used to construct the correct API endpoint URLs for your account (e.g., https://{data_center}.api.mailchimp.com/3.0/). The API key provides access to your Mailchimp account data and should be treated as sensitive information. If your API key is compromised, you should immediately revoke it in your Mailchimp account settings (Account > Extras > API keys) and generate a new one. For detailed information about obtaining API keys, API authentication, and available endpoints, refer to the Mailchimp Developer Documentation.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| Data Center | Yes | No | Data Center |
| API Key | Yes | Yes | API Key |
Create a credential in Nexla
- After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Mailchimp

-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Mailchimp uses Basic Authentication for all API requests, where the API key is used as the password and any string can be used as the username. Enter your Mailchimp data center identifier in the Data Center field. This should be the subdomain from your Mailchimp account URL (e.g.,
us1,us2,us3, etc.). The data center identifies the geographic location of your account's data and is used to construct API endpoint URLs (e.g.,https://{data_center}.api.mailchimp.com/3.0/). -
Enter your Mailchimp API key in the API Key field. This is the API key you obtained from your Mailchimp account settings (Account > Extras > API keys). The API key is used as the password in Basic Authentication for all API requests to the Mailchimp API and must be kept confidential.
Your Mailchimp API key can be found in your Mailchimp account settings (Account > Extras > API keys). The API key is used with Basic Authentication for all API requests to the Mailchimp API, where the API key is used as the password and any string can be used as the username. The data center is used to construct the correct API endpoint URLs for your account.
If your API key is compromised, you should immediately revoke it in your Mailchimp account settings (Account > Extras > API keys) and generate a new one. The API key provides access to your Mailchimp account data and should be treated as sensitive information. Keep your API key secure and do not share it publicly.
For detailed information about obtaining API keys, API authentication, and available endpoints, see the Mailchimp Developer Documentation.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Mailchimp connector tile, then select the credential that will be used to connect to the Mailchimp instance, and click Next; or, create a new Mailchimp credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Mailchimp endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Mailchimp data sources can also be manually configured to ingest data from any valid Mailchimp API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Mailchimp API endpoints follow the pattern https://{data_center}.api.mailchimp.com/3.0/{endpoint_path}, where {data_center} is your account's data center identifier (e.g., us1). For responses that nest the relevant records inside a top-level key — for example, the lists array returned by the Lists endpoint — enter the corresponding path (e.g., $.lists[*]) in the Set Path to Data in Response field. For a complete list of available Mailchimp API endpoints, see the Mailchimp API Documentation.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Mailchimp data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Use as a destination
Click the + icon on the Nexset that will be sent to the Mailchimp destination, and select the Send to Destination option from the menu. Select the Mailchimp connector from the list of available destination connectors, then select the credential that will be used to connect to the Mailchimp organization, and click Next; or, create a new Mailchimp credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Mailchimp endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Manual configuration
Mailchimp destinations can also be manually configured to send data to any valid Mailchimp API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Mailchimp APIs typically expect JSON format for most operations. For update/upsert operations, include the ID of the object to be updated at the end of the URL.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Mailchimp endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Mailchimp endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.