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, andX-RateLimit-Reset, when the current window ends. - Over the budget, the answer is
429 RateLimitedwith aRetry-Afterheader in seconds. Wait that long, then send the request again, with the sameIdempotency-Keyif it had one. - Spread bulk work out over time instead of sending it in one burst, and read
GET /postsin 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 /usagereturns the workspace's meters for the current billing period against the plan's limits.GET /usage/dailycounts 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
| Plan | Requests per minute | Connected accounts | Posts per month | Logs and events kept |
|---|---|---|---|---|
| Free | 60 | 2 included, up to 2 | 50 | 7 days |
| Pro | 600 | 10 included, up to 60 | No limit | 30 days |
| Business | 1,200 | 100 included, more on request | No limit | 90 days |
| Enterprise | 1,200 | 100 included, more on request | No limit | 90 days |