Skip to main content

Rate Limit Overview

  • Limit: 1000 requests per hour per API key
  • Window: Rolling 1-hour window
  • Scope: Applied per API key across all endpoints
Rate limits are applied per API key, so each key gets its own 1000 requests per hour allocation.

Rate Limit Headers

Every API response includes rate limit information in the response headers:

Header Descriptions

X-RateLimit-Limit
integer
required
Maximum number of requests allowed per hour
X-RateLimit-Remaining
integer
required
Number of requests remaining in the current hour
X-RateLimit-Reset
integer
required
Unix timestamp when the rate limit resets

Rate Limit Exceeded Response

When you exceed the rate limit, you’ll receive a 429 status code with an error response:

Best Practices

Implement Exponential Backoff

When you receive a 429 response, implement exponential backoff to retry your requests:

Monitor Your Usage

Track your API usage to avoid hitting rate limits:

Batch Operations

When possible, batch multiple operations to reduce the number of API calls:
Instead of making individual API calls for each vehicle, consider batching operations or using bulk endpoints when available.

Request Optimization Tips

Cache Responses

Cache frequently accessed data like location information:

Use Appropriate Endpoints

Choose the most efficient endpoint for your use case:
  • Use filtering parameters to reduce data transfer
  • Use specific endpoints instead of general ones when possible
  • Consider pagination for large datasets

Rate Limit Increase

If you need a higher rate limit for your use case, contact hello@arqqin.com with:
  • Your current usage patterns
  • Expected request volume
  • Business justification for the increase
Rate limit increases are evaluated on a case-by-case basis and may require a different pricing tier.

Monitoring and Alerts

Set up monitoring to track your API usage:
Monitor your API usage with:
  • Track requests per hour
  • Set up alerts when approaching limits
  • Monitor error rates and retry patterns
  • Log rate limit headers for analysis
Implement proper error handling for:
  • 429 rate limit responses
  • Network timeouts
  • Temporary service unavailability
  • Invalid responses