Rate Limits & Quotas

All API calls enforce rate limits to protect platform stability. This guide explains the limits you can expect and how to design integrations that scale gracefully.

Standard Limits

Limits apply per workspace. The response headers include remaining quota:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1731523620

X-RateLimit-Reset is a Unix timestamp indicating when the bucket refills.

Handling 429 Responses

When you exceed a limit, the API returns 429 Too Many Requests with an error payload:

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Too many requests to /posts. Try again in 30 seconds.",
    "retryAfter": 30
  }
}

Respect the Retry-After header before retrying. Exponential backoff (1s, 2s, 4s, 8s) is recommended for sustained traffic.

Best Practices

• Batch Requests: Use pagination and batch endpoints (/posts/batch, /analytics/batch) to reduce call volume.
• Cache Responses: Store frequently accessed data locally for short periods instead of requesting repeatedly.
• Queue Writes: Schedule publishing operations through a queue to smooth spikes.
• Parallelism with Limits: If streaming high volumes, cap concurrent requests to the documented burst value.

Exceeding Limits Frequently?

• Review request patterns using the Integration Usage dashboard in Workspace Settings.
• Contact support with your use case if you need higher limits; enterprise plans can receive custom quotas.
• Ensure you are filtering analytics queries to the exact data needed—large date ranges consume more quota.

For error payload structure and troubleshooting tips, continue to Error Codes & Troubleshooting.