To ensure fair and consistent API performance for all clients, Tupel enforces rate limits on all API endpoints, preventing excessive usage that could impact system stability.
Default Limits
By default, each authenticated API key is limited to:
- 60 requests per minute
Rate Limit Exceeded
If you exceed the rate limit, you'll receive:
- HTTP status code
429 Too Many Requests - A JSON response with an error message
Handling Rate Limits
To prevent disruptions due to rate limits, follow these best practices:
- Monitor rate limit headers in API responses to track usage
- Implement exponential backoff strategies to retry requests efficiently
- Queue requests and execute them progressively when limits are reached
- Distribute requests over time instead of sending bursts of traffic
Increased Rate Limits
Need a higher request quota? We offer increased rate limits upon approval. Contact developers@tupel.com with details about:
- Your use case
- Expected request volumes
- Justification for higher limits
Best Practices
- Cache responses to reduce redundant API calls and improve performance
- Batch operations to minimize individual requests and increase efficiency
- Use exponential backoff for retries to avoid excessive requests
- Prefer webhooks over polling to receive real-time updates with minimal API calls