Skip to main content
The YuvexPay API enforces rate limits per company to ensure fair usage and system stability.

Default limits

Custom limits can be configured per account. Contact support if you need higher limits.

Rate limit headers

Every API response includes rate limit information in the headers:

Handling rate limits

When you exceed the rate limit, the API returns a 429 Too Many Requests response:
Implement exponential backoff when you receive a 429:

Best practices

  • Monitor headers. Check X-RateLimit-Remaining proactively to avoid hitting limits.
  • Batch where possible. Use list endpoints with filters instead of fetching resources one by one.
  • Cache responses. Cache GET responses on your side to reduce unnecessary API calls.
  • Spread requests. Distribute API calls evenly over time instead of bursting.