Rate limits
How many requests you can make and how to read the limit headers.
| Limit | Value |
|---|---|
| Production key | 120 requests per minute |
| Sandbox key | 60 requests per minute |
| Per client IP, all keys combined | 300 requests per minute |
| Request body | 32 KB |
Limits use fixed one-minute windows per key. Every authenticated response includes:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Requests allowed in the current minute. |
X-RateLimit-Remaining | Requests left in the current minute. |
X-RateLimit-Reset | When the window resets, as Unix epoch seconds. |
Above the limit you get 429 RATE_LIMIT_EXCEEDED with a Retry-After header in seconds. Wait that long before the next request.
Staying under the limit
- Cache
GET /v3/mobile/plansandGET /v3/internet/productsfor a few minutes instead of calling them on every order. - Poll each pending top-up every 5 to 10 seconds, not faster.
- Use the list endpoints for reporting instead of one
check-idper top-up. GET /v3/pingneeds no key and is limited only per IP. Call it at most every 30 seconds.
Need more? Contact support with your expected volume.