Current Rate Limits
| Endpoint | Limit | Window |
|---|---|---|
| POST /process/ | 100 requests | per minute |
| GET /transactions/ | 300 requests | per minute |
Rate Limit Headers
Rate limit headers are included in responses:| Header | Example Value | Description |
|---|---|---|
X-RateLimit-Limit | 100 | Request limit per window |
X-RateLimit-Remaining | 95 | Requests remaining in the current window |
X-RateLimit-Reset | 1640995200 | Unix timestamp when the limit resets |
Rate Limit Response
When rate limited, the API returns HTTP 429 with retry information:Basic Limit Handling
When you receive a 429 response, do the following:- Check the
retry_afterfield in the error response - Wait the specified time before retrying
- Monitor rate limit headers to prevent hitting limits
- Implement exponential backoff for failed requests
Example Response Handling (Python)
Example Response Handling (Python)
Best Practices
These are some best practices to follow when handling rate limits.- Track your API usage against limits
- Use exponential backoff for retries
- Cache when possible to reduce unnecessary API calls
- Batch multiple operations when supported
Next Steps
- Review Error Handling for rate limit error management
- Check Production Readiness for monitoring setup
- Contact Support for rate limit increase requests