Rate Limits

API Request Limits

Rate limits are applied per API key based on your plan:

Rate Limit Headers

Every API response includes these headers:

Handling Rate Limits

When you exceed the limit, the API returns 429 Too Many Requests:

{
  "error": "Rate limit exceeded. Please try again later."
}

Best approach: check X-RateLimit-Remaining before making requests, and back off when it's low. If you receive a 429, wait until X-RateLimit-Reset before retrying.

Posting Velocity Limits

Independent of API rate limits, there are limits on how fast you can publish posts to prevent platform-level throttling:

These limits protect your accounts from being flagged by social platforms. If a post is rejected due to velocity limiting, you'll receive an error explaining the cooldown period.

Tools Endpoints

The Tools endpoints (downloads, transcripts, hashtag checker) have their own daily limits:

Track your tool usage via the Usage Stats endpoint.

Analytics Data Freshness

Analytics endpoints have their own caching and refresh behavior rather than strict rate limits:

• Post analytics - Cached for 60 minutes. Requests trigger a background refresh if cache is stale. No rate limit on API requests.
• Follower stats - Refreshed once per day automatically.
• YouTube daily views - Data has a 2-3 day delay from YouTube's Analytics API.

See the Analytics endpoints for details.

Tips for Staying Within Limits

• Use pagination - Don't fetch all resources at once. Use limit and offset parameters.
• Cache responses - Store data locally instead of re-fetching frequently.
• Use webhooks - Subscribe to webhooks instead of polling for post status changes.
• Batch operations - Use bulk upload instead of creating posts one at a time.