This article lists the Mailchimp Marketing API endpoints the iPaaS.com Mailchimp integration calls when it sends records to Mailchimp. Every flow in this integration runs in one direction only — from iPaaS.com to Mailchimp — so the endpoints below are the create, update, and delete operations the integration uses to write Audience members and e-commerce records into your Mailchimp account.

All paths, methods, authentication, and limits are sourced from Mailchimp's published Marketing API reference (version 3.0). Mailchimp documentation cited in this article was reviewed on 2026-06-29.

The Mailchimp Marketing API is served from a data-center-specific host. The base URL has the form:

The

(also called the data center) is the short code at the end of your Mailchimp API key, after the final hyphen — for example, a key ending in -us13 uses the host https://us13.api.mailchimp.com. The integration builds this base URL from the API Url and API Key values you enter in the Subscription Settings, so you do not construct it by hand; you only need to confirm that the API Url you enter matches the server prefix shown in your Mailchimp account's API key area.

(Source: Mailchimp Marketing API — Authentication / Fundamentals, https://mailchimp.com/developer/marketing/docs/fundamentals/, reviewed 2026-06-29.)

In the endpoint tables below, [Base URL] represents https://

.api.mailchimp.com.

The integration authenticates to the Mailchimp Marketing API using your Mailchimp API key. Mailchimp accepts the key two ways, and the integration uses one of them on your behalf; you do not need to configure the scheme manually:

You only supply the API Key in the Subscription Settings. There is no separate OAuth login step for this integration.

(Source: Mailchimp Marketing API — Authentication / Fundamentals, https://mailchimp.com/developer/marketing/docs/fundamentals/, reviewed 2026-06-29.)

The Customer flow writes contacts into a Mailchimp Audience (List) as members. Each member is created or updated against the Audience identified by the List Id you map.

Create a Member (POST):

Path parameter: list_id (the Mailchimp Audience/List Id). Required body fields: email_address and status.

Update a Member (PATCH):

Path parameters: list_id and subscriber_hash. The subscriber_hash is the MD5 hash of the lowercased email address; the integration computes this for you. A PATCH applies only the fields supplied, so values you do not map are left untouched.

(Source: Mailchimp Marketing API — List Members: Add member to list / Update list member, https://mailchimp.com/developer/marketing/api/list-members/, reviewed 2026-06-29.)

When an order is processed, the integration ensures the order's customer exists as an e-commerce customer in the relevant store before the order is created. These customer writes happen automatically as a prerequisite of the order flow.

Create a Customer (POST):

Update a Customer (PATCH):

Path parameters: store_id (the Mailchimp store) and, for updates, customer_id.

(Source: Mailchimp Marketing API — E-commerce Stores: Customers, https://mailchimp.com/developer/marketing/api/ecommerce-customers/, reviewed 2026-06-29.)

The Order (Transaction) flow creates and updates e-commerce orders within a Mailchimp store.

Create an Order (POST):

Path parameter: store_id. Required body fields: id, customer, currency_code, order_total, and lines.

Update an Order (PATCH):

Path parameters: store_id and order_id. A PATCH applies only the supplied fields.

Order id values are limited to 49 characters or fewer; longer values are rejected before the request is sent. Order lines are written as part of the order payload, so there is no separate order-line write endpoint.

(Source: Mailchimp Marketing API — E-commerce Stores: Orders: Add order / Edit order, https://mailchimp.com/developer/marketing/api/ecommerce-orders/, reviewed 2026-06-29.)

The Product flow creates, updates, and deletes e-commerce products within a Mailchimp store.

Create a Product (POST):

Path parameter: store_id. Required body fields: id, title, and variants (a product is always created with at least one variant).

Update a Product (PATCH):

Delete a Product (DELETE):

Path parameters for update and delete: store_id and product_id.

(Source: Mailchimp Marketing API — E-commerce Stores: Products: Add product / Update product / Delete product, https://mailchimp.com/developer/marketing/api/ecommerce-products/, reviewed 2026-06-29.)

The Product Variant flow creates, updates, and deletes variants under a specific product within a store.

Create a Variant (POST):

Required body fields: id and title.

Update a Variant (PATCH):

Delete a Variant (DELETE):

Path parameters: store_id, product_id, and, for update and delete, variant_id. The parent product must already exist and be linked in Mailchimp before a variant can be written.

(Source: Mailchimp Marketing API — E-commerce Stores: Product Variants: Add / Update / Delete product variant, https://mailchimp.com/developer/marketing/api/ecommerce-product-variants/, reviewed 2026-06-29.)

The integration sends records to Mailchimp one at a time using the create, update, and delete endpoints above, so it does not page through Mailchimp result sets as part of normal record transfer. Where Mailchimp's Marketing API does return lists (for example, when looking up an existing record), the API uses count and offset query parameters and returns a total_items value in the response envelope. The integration handles any such lookups internally; you do not configure paging.

(Source: Mailchimp Marketing API — Fundamentals, https://mailchimp.com/developer/marketing/docs/fundamentals/, reviewed 2026-06-29.)

Mailchimp's Marketing API enforces a limit of 10 simultaneous connections. Requests beyond that limit receive an HTTP 429 response, and Mailchimp may disable API access if the limit is exceeded repeatedly. Individual API calls are also subject to a 120-second timeout. Plan large or recurring transfers so they do not run many concurrent jobs against the same Mailchimp account at once.

(Source: Mailchimp Marketing API — Fundamentals, https://mailchimp.com/developer/marketing/docs/fundamentals/, reviewed 2026-06-29.)