Rate limits
Request limits per API key, per endpoint, and how they relate to platform posting quotas.
Preview
Preview: the API and MCP server are in private beta; details may change.
Rate limits protect the API from bursts of requests; they are separate from the platform posting quotas described in Platform rules.
Current limits
| Scope | Limit |
|---|---|
| Per API key | 120 requests per minute |
POST /posts | 30 requests per minute |
Every response includes:
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 113
X-RateLimit-Reset: 1759058460
A request over the limit returns 429 with a Retry-After header telling you how many seconds to wait.
Platform quotas are separate
Instagram's 100 posts per day, Threads' 250 posts per day, and TikTok's roughly 15 posts per day are platform level quotas, not API rate limits. They are enforced before a post is queued and returned as quota_exceeded (see Errors), and the current remaining quota per account is visible at GET /accounts/{id} in the quota field.
Practical advice
- Check
X-RateLimit-Remainingbefore firing a large batch of individualPOST /postscalls; when scheduling many posts at once, preferPOST /posts/batch(up to 31 items) over callingPOST /postsin a loop. - Back off using
Retry-Afterrather than a fixed delay; it reflects the actual reset window. platform_unavailableerrors (see Errors) are retryable and already get IMMA AI's own internal retry; you generally do not need to retry these yourself.