Rate Limits
Hard rate limits are not active in the dev environment. Production limits will be published before the production environment opens.
Current status
| Environment | Status |
|---|---|
| Dev (api-dev.pryzma.global) | No hard limits — for development use |
| Production | Limits TBD — announced before launch |
Recommended practices
Even without enforced limits, follow these guidelines to avoid issues:
- Maximum 10 requests per second per credential in steady state
- Burst headroom: short bursts up to 30 rps are fine; sustained load above 10 rps is not
- Idempotent retries: use the
Pryzma-Idempotency-Keyheader on all mutating requests so you can safely retry without duplicating operations
429 response
When rate limits are active, exceeding your quota returns:
HTTP 429 Too Many Requests
Retry-After: 1
The Retry-After header specifies the number of seconds to wait before retrying. Honour this value rather than retrying immediately.
Upcoming
Production rate limits will be based on:
- Per-credential request rate (rps)
- Per-organisation monthly volume (number of transfers)
Details will be published in the Changelog when the production environment opens.