Guides

Rate limits

How many requests each API accepts, and what to do when one is refused with a 429.

Each API counts requests its own way, described here as it behaves. Every 429 carries a Retry-After header: wait that many seconds, then send the request again. A refused request did nothing, so sending it again is safe.

Dynamic Audience API

60 requests per minute per API key, and 60 per minute from one source address.
Over either limit: HTTP 429 with rate_limited and a Retry-After of 60 seconds.
One request can carry up to 5,000 recipients, so send them in batches rather than one request per recipient when you have many.

rate_limited429

HTTP/1.1 429 Too Many Requests
Retry-After: 60

{
  "code": "rate_limited",
  "message": "Too many requests. Wait a moment and try again."
}

Integrations push API and Integrations MCP server

About 120 requests per minute per source IP, counted together across the push API and the Integrations MCP server. The count is kept per server instance, so the exact point can vary.
Over the limit: HTTP 429 with rate_limited and a Retry-After of 60 seconds.
One batch can carry up to 1,000 records, so a daily sync needs few requests.

rate_limited429

HTTP/1.1 429 Too Many Requests
Retry-After: 60

{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Slow down and retry."
  }
}