API Reference
Rate limits
Per-account request limits, and what to do when you hit one.
Rate limits apply per account, not per token — issuing a second token does
not raise the limit. Exceeding a limit returns
429.
| Endpoints | Limit |
|---|---|
| All CMS endpoints | 120 requests per minute, shared |
POST /v1/analytics/export | 3 per minute, and 20 per day |
| All other endpoints | No documented per-endpoint limit |
The CMS limit is shared across every CMS endpoint, so a burst of entry writes consumes the same budget as listing collections.
Staying under the limit
Batch where the API allows it
Reporting conversions accepts an array, so a batch of 50 conversions is one request rather than 50.
Page with a sensible size
List endpoints return up to 100 results per request. Fetching 100 at a time uses a fifth of the requests that fetching 20 at a time would.
Poll jobs slowly
An analytics export takes time to produce. Poll its job every few seconds, not continuously.
Back off on 429
Wait for the window to pass before retrying. Retrying immediately keeps you over the limit for longer.
The export limit is a daily budget
Analytics exports are capped at 20 per day per account. A job that retries on every failure can exhaust the day's budget in minutes — retry deliberately.