Rate Limiting
LIVEQuick Summary
Rate limiting protects the API from excessive use by capping the number of requests
you can make within a given time period. Limits are applied per API key.
Exceeding the limit returns a 429 Too Many Requests response.
Rate Limits
The following limits apply to each API key. Limits reset at the start of each new window.
| Endpoint Type | Limit | Window | Description |
|---|---|---|---|
| All Endpoints | 60 requests | Per minute | Applies to all authenticated requests — balance checks, purchases, verifications, and test endpoints |
| Unauthenticated / IP Fallback | 10 requests | Per minute | Applied when no valid API key is present |
When You Hit the Limit
If you exceed the rate limit, the API returns a 429 Too Many Requests response.
You should pause requests until the window resets.
Error Response (429)
{
"code": 429,
"status": "error",
"message": "Too many requests. Please try again later."
}Best Practices
Cache Responses
Cache balance and provider lists that don't change frequently to reduce API calls.
Implement Retry Logic
If you receive a 429 response, wait before trying again.
Use Unique References
Send unique references with each purchase to safely retry without creating duplicate transactions.
Batch Wisely
Group non-urgent requests where possible to stay comfortably within your limit.
Pro Tip
If you need higher rate limits for your application, contact our support team to discuss your requirements. We're happy to work with you.