IMMA AI Docs

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

ScopeLimit
Per API key120 requests per minute
POST /posts30 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-Remaining before firing a large batch of individual POST /posts calls; when scheduling many posts at once, prefer POST /posts/batch (up to 31 items) over calling POST /posts in a loop.
  • Back off using Retry-After rather than a fixed delay; it reflects the actual reset window.
  • platform_unavailable errors (see Errors) are retryable and already get IMMA AI's own internal retry; you generally do not need to retry these yourself.

On this page