Developers
Rate limits
One token bucket per API key. Limits exist to protect everyone's social-channel quotas, not just our backend.
v1 limits
The bucket starts full, so a quiet key can spend a whole minute's allowance at once; sustained throughput then settles at the steady-state rate for your plan.
When you hit the limit
The response is 429 rate_limited with a Retry-After header giving the number of seconds before the next attempt is allowed.
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 3
{ "error": { "code": "rate_limited", "message": "Slow down." } }Best practice
- Honor
Retry-Afterverbatim. Don't retry sooner — you'll just stay banned longer. - Cap parallelism on your side; the limit is server-wide per key, not per worker.
- Burst is for short spikes like backfilling a batch of posts, not for sustained throughput.