# Rate limits

> Request budgets per workspace and plan, per-operation limits, the RateLimit headers, network limits and how to handle 429 responses.

The public API and the MCP server share one hourly request budget per workspace. All of a workspace's API keys and OAuth connections count against it.

| Plan | Requests per hour |
|---|---|
| Free | 600 |
| Pro | 6,000 |
| Business | 30,000 |
| Enterprise | 120,000 or more |

Every response carries the current state:

- `RateLimit-Limit`: the budget for the window.
- `RateLimit-Remaining`: requests left in the window.
- `RateLimit-Reset`: seconds until the window resets.

When the budget is spent, the API answers `429` with `rate_limit_error` and a `Retry-After` header (seconds). Wait that long, then retry; back off exponentially if it happens again. `GET /v1/usage` shows the current window.

## Other limits

| Limit | Error |
|---|---|
| Some operations have their own, tighter bucket (for example re-verification codes, test sends) | `429 rate_limit_error` with `Retry-After` |
| Posts per account per day (plan) | `429 posts_per_day_limit` with `usage` |
| A network's own limit (posts per day on TikTok or Instagram, YouTube quota units, Reddit QPM) | `429 platform_rate_limited` with `Retry-After`, or a `platform_error` |
| Messaging pace of broadcasts per channel | Paced automatically, see [Broadcasts](/docs/crm-automations/#broadcasts) |

> **Tip:** Use [webhooks](/docs/webhooks/) and `GET /v1/analytics/delta` instead of polling, and [idempotency keys](/docs/api-reference/idempotency/) so retries after a 429 are safe.

---

Source: https://socialit.com/docs/api-reference/rate-limits/
