Skip to main content
To ensure the stability and reliability of the xChangeAPI platform, we have implemented measures to regulate traffic during bursts of activity. These limiters, including a requests-per-second rate limiter, help prevent abuse and ensure fair usage for all clients.

​
Rate Limiting Logic

If your application sends too many requests in quick succession, the API will respond with an HTTP error status code.
  • Status Code: 429 Too Many Requests
  • Mechanism: Limits are calculated based on the number of requests received per second.
  • Scope: Limits may vary across different API endpoints depending on the complexity of the data being requested.

​
Monthly Request Limits

In addition to the rate limits per second, your API usage is also subject to a monthly quota based on your subscription plan. These limits ensure fair resource allocation and help you choose the right plan for your application’s scale.
For detailed information on the specific monthly limits for each plan, please refer to our Pricing Page.
If you exceed your monthly request limit, the API will return an error indicating that your quota has been exhausted. You can upgrade your plan at any time to increase your monthly allowance.

​
Handling Rate Limits

To avoid service interruptions, we recommend designing your application to handle 429 errors gracefully.
Best Practice: Exponential BackoffIf you receive a 429 response, do not immediately retry the request. Instead, implement a retry logic with exponential backoff. Wait for a short period, then retry. If it fails again, wait longer before the next attempt.

​
Requesting Limit Increases

We understand that high-traffic applications may require throughput that exceeds our standard limits.
  • Unexpected Spikes: If you notice a sudden spike in rate-limited requests that affects your legitimate workflow, please contact support immediately.
  • Planned Increases: If you anticipate a need for a permanently higher rate limit (e.g., for a new product launch or scaling up), we can adjust parameters to support your needs.
Advance Notice RequiredFor planned limit increases, you must contact support at least 3 days in advance. This allows us to allocate the necessary infrastructure resources to maintain stability.