Mailchimp Rate Limits
Mailchimp rate-limits the Marketing API by CONCURRENCY, not by a request quota over a window. There is no published per-minute or per-hour ceiling, and — the finding that matters most for an agent — the API returns NO rate-limit response headers at all. A client cannot read how much budget it has left; it can only hold its own concurrency below 10 and react to a 429. At very high volume the throttle can also surface as a bare 403 with no JSON body, which a naive client will misread as an authorization failure.
Mailchimp Rate Limits is the rate-limit profile for Mailchimp on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-08-13.
It captures 4 rate-limit definitions, including Concurrent API connections — The Marketing API has a limit of 10 simultaneous connections.; Open batch operations — Batch requests are limited to 500 pending requests; Webhook callback response time — takes more than 10 seconds to respond.
An exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, throttled_alternate, and throttled_alternate_note.
Tagged areas include Rate Limiting and Email.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.