Skip to content
Relay Port

Events and limits

Rate limits and plans

The request budget each workspace has per minute, the headers that report it, and the plan limits on accounts, posts and log retention.

The request budget

Each workspace has one budget of requests per minute, shared by all of its API keys and the Dashboard. The size of the budget depends on the plan: see the table under this guide.

  • Every response carries X-RateLimit-Limit, the budget, and X-RateLimit-Reset, when the current window ends.
  • Over the budget, the answer is 429 RateLimited with a Retry-After header in seconds. Wait that long, then send the request again, with the same Idempotency-Key if it had one.
  • Spread bulk work out over time instead of sending it in one burst, and read GET /posts in pages of up to 100 instead of one request per post.

Plan limits

Plans also limit how many accounts a workspace can connect, how many posts it can create per month and how long its request logs and events are kept. When a request would go past a limit, the answer is 402 PlanLimitReached and nothing is created.

  • GET /usage returns the workspace's meters for the current billing period against the plan's limits.
  • GET /usage/daily counts the targets created, published and failed per day.

Publishing budgets

Separate from the request budget, each social account has publishing budgets that come from its platform, such as how many posts it can publish in a day. Those are per account, not per workspace: see Publishing to Instagram.

Limits by plan

PlanRequests per minuteConnected accountsPosts per monthLogs and events kept
Free602 included, up to 2507 days
Pro60010 included, up to 60No limit30 days
Business1,200100 included, more on requestNo limit90 days
Enterprise1,200100 included, more on requestNo limit90 days