Throttling

Overview

To ensure fair usage and system stability, rate limits are enforced. This document provides details on the rate limits applied to Hadron by Tether API.

Rate Limits

Hadron by Tether API applies throttling and quotas to regulate API usage. The rate limits are categorized as follows:

1. Throttle Limits

Throttle limits are applied at the API Gateway level to control requests per second.

• Rate Limit: 100 requests per second
• Burst Limit: 200 requests

These limits help prevent sudden traffic spikes from affecting API performance.

2. Quota Limits

Quota limits define the maximum number of requests a client can make in a given period.

Daily Quota: 1000 requests per day

If a quota is exceeded, subsequent requests will receive an HTTP 429 Too Many Requests response.

Error Responses

If a client exceeds the rate limits, the API Gateway will return an HTTP 429 status code with the following response format:

{
  "message": "Rate limit exceeded. Please try again later."
}

Best Practices

To ensure uninterrupted access to Hadron by Tether API, follow these best practices:

1. Optimize API Calls: Reduce unnecessary requests by caching responses where applicable.
2. Implement Retry Logic: Use exponential backoff when handling 429 responses.
3. Monitor Usage: Track API consumption using AWS CloudWatch logs and API Gateway metrics.