Limits and errors
Request limit
Section titled “Request limit”100 requests per minute per credential, adding up all routes of v1 and of the legacy API.
- It is counted by public key (
x-public-key). Two credentials on the same server have separate limits; a shared IP does not mix clients. - The legacy API’s transaction and subscription lookups have their own, lower ceiling: 30 per minute.
- Every response carries
X-RateLimit-Limit,X-RateLimit-RemainingandX-RateLimit-Reset(seconds until the limit resets). - Above the limit, the response is
429withRetry-After(seconds).
Do not poll. To know when a sale was paid, use webhooks.
v1 errors
Section titled “v1 errors”{ "statusCode": 404, "message": "Venda não encontrada.", "error": "Not Found" }Error messages are in Portuguese; rely on statusCode, not on the text.
| Status | When |
|---|---|
400 |
invalid parameter (for example page=abc or page=0; page_size above 100 is capped at 100) |
401 |
missing, invalid, revoked or expired credential (same message in all four cases) |
403 |
the credential lacks the route’s permission |
404 |
does not exist, or is not in your account |
429 |
request limit (see above) |
503 |
scheduled maintenance, with Retry-After |
5xx |
our failure. Retry with exponential backoff. |
The legacy API keeps the previous platform’s error format: see Legacy API.

