CoinVoyage applies rate limits to keep payment flows reliable during traffic spikes, retries, and abusive request patterns. Limits vary by endpoint and credential type.
429 responses
When a request exceeds a limit, CoinVoyage returns 429 Too Many Requests:
HTTP/1.1 429 Too Many Requests
Retry-After: <seconds>
{
"error": "Too Many Requests",
"message": "Rate limit exceeded. Please try again later.",
"code": 429
}
Retry-After is present, wait at least that many seconds before retrying.
Retry guidance
- Respect
Retry-After instead of retrying immediately.
- Add jitter when multiple workers or browser tabs may retry the same operation.
- Use bounded exponential backoff for network failures and
5xx responses.
- Retry reads more freely than create or mutation requests.
- Keep fulfillment and reconciliation idempotent by PayOrder ID.
Use webhooks for payment state changes. Polling is useful for dashboard views and reconciliation jobs, but webhooks should be the primary completion signal.
