Getting Started
Rate Limiting
Understanding API rate limits and best practices
Overview
API requests are rate limited to ensure stability and fair usage for all users.Rate Limit
API Rate Limit
100 requests per minuteAll API keys are subject to this rate limit to ensure fair usage and stability.
Rate Limit Headers
Every API response includes headers with rate limit information:| Header | Description |
|---|---|
X-RateLimit-Limit | The maximum number of requests allowed |
X-RateLimit-Remaining | The number of requests remaining |
X-RateLimit-Reset | The time when the rate limit resets (Unix timestamp) |
Handling Rate Limits
When you exceed the rate limit, you’ll receive a429 Too Many Requests response:
retry_after field indicates how many seconds to wait before retrying.
Best Practices
Implement Exponential Backoff
Implement Exponential Backoff
When rate limited, implement exponential backoff:
Cache Responses
Cache Responses
Cache frequently accessed data to reduce API calls:
- Client lists that don’t change often
- Product catalogs
- Static configuration data
Batch Operations
Batch Operations
Where possible, use batch operations:
- Create multiple invoices in a single request
- Fetch data with appropriate pagination limits
Monitor Usage
Monitor Usage
Track your API usage:
- Log rate limit headers
- Set up alerts for high usage
- Plan for traffic spikes
Increasing Rate Limits
If you need higher rate limits for your application:- Contact support at contact@contazen.ro
- Provide details about your use case
- Include your current usage patterns
- Explain expected growth