Rate limits
How much you can call, and what happens when you go over.
| Limit | Value |
|---|---|
| Calls per token | 120 per minute, across all endpoints |
| Actions per account (generate keys and reset HWID) | 30 per minute, across the panel and every token |
| Keys per generation call | 50 |
| Transactions per statement page | 200 |
Keys per lookup with user_ids[] | 200 |
| Active tokens per account | 10 |
When you go over
The response is 429, with the Retry-After header saying how many seconds to wait. The message says the same time (in Portuguese):
HTTP/1.1 429 Too Many Requests
Retry-After: 55
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 0{
"success": false,
"message": "Muitas requisições. Tente de novo em 55 segundo(s).",
"errors": []
}Successful responses carry X-RateLimit-Limit (the limit) and X-RateLimit-Remaining (what is left) for the limit closest to running out. Use Remaining to slow down before reaching 429.
How to stay under the limit
- Cache the product list for a few minutes instead of fetching it on every sale.
- Look up only the keys you need, with
user_ids[]. - Prefer webhooks to polling the API.
- For large batches, generate up to 50 keys per call instead of one at a time.