Skip to main content
The Chariow API implements rate limiting to ensure fair usage and maintain service quality for all users.

Default Limits

Rate limits are applied per API key. Each API key has its own separate limit counter.

Rate Limit Headers

Every API response includes headers indicating your current rate limit status:

Rate Limit Exceeded

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:
The response includes a Retry-After header indicating how long to wait:

Handling Rate Limits

Exponential Backoff

Implement exponential backoff to gracefully handle rate limits:

Request Batching

Batch multiple operations to reduce request count:

Caching

Cache responses to avoid unnecessary requests:

Increasing Limits

If you need higher rate limits:
  1. Enterprise Plans - Higher limits are available on enterprise plans
  2. Contact Support - Request a temporary increase for specific use cases
  3. Optimize Usage - Review your implementation for optimization opportunities
Contact support@chariow.com to discuss higher rate limits for your use case.

Best Practices

Track rate limit headers to understand your usage patterns and adjust accordingly.
Instead of polling for changes, use webhooks to receive real-time notifications.
Queue requests and process them at a controlled rate to avoid bursts.
Cache data that doesn’t change frequently to reduce API calls.