Rate Limits¶
Overview¶
The Pontotel API implements rate limiting to ensure availability and performance for all clients.
What is Rate Limiting?
Rate limiting is a technique that limits the number of requests a client can make in a specific time period.
Current Limits¶
| Environment | Limit | Window | Burst |
|---|---|---|---|
| Sandbox | 1000 requests | 1 hour | 100/min |
| Production | 500 requests | 1 hour | 50/min |
Rate Limit Headers¶
Each API response includes informational headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Total request limit |
X-RateLimit-Remaining | Remaining requests |
X-RateLimit-Reset | Unix timestamp when limit resets |
429 Response (Too Many Requests)¶
When the limit is exceeded:
| JSON | |
|---|---|
Status Code: 429 Too Many Requests
Additional header:
| HTTP | |
|---|---|
Best Practices¶
1. Monitor Headers¶
2. Implement Retry with Backoff¶
3. Response Caching¶
Reduce requests by caching responses:
4. Batch Requests¶
Group multiple operations when possible:
| Python | |
|---|---|
5. Efficient Pagination¶
Use pagination to avoid unnecessary requests:
Increase Limits¶
If you need higher limits:
- Contact commercial support
- Present your use case
- Consider plan upgrade
Enterprise Plans
Enterprise plans offer:
- Custom rate limits
- Higher burst
- Guaranteed SLA
- Priority support
Monitoring¶
Recommended Dashboard¶
Monitor important metrics:
- Requests per hour
- 429 error rate
- Average response time
- Rate limit usage percentage
Alerts¶
Configure alerts for:
- 80% of rate limit reached
- Consecutive 429 errors
- Response time > 2s