Rate limits & throttling
Endpoint limits
Most endpoints share a general limit. Heavier endpoints have their own:
| Endpoint | Limit |
|---|---|
GET …/export (orders, settlements, statements CSV) | 5 / min |
GET …/{periodMonth}/pdf | 5 / min |
POST …/confirm-payment | 10 / min |
The 429 response is different
429 has no
codeA throttle response does not use the problem+json shape and has no code
field. It looks like:
{ "statusCode": 429, "message": "Too many requests" }
Handle it by branching on the HTTP status first:
if (status == 429) → back off and retry (respect Retry-After if present)
else → parse problem+json and switch on `code`
Use exponential backoff with jitter (e.g. 1s, 2s, 4s, 8s…). Don't tight-loop retries, and poll exports with backoff rather than hammering.