Rate Limits
The Wallbit API implements rate limiting to ensure fair usage and maintain service stability for all users.Current Limits
| Tier | Requests per Minute | Requests per Day |
|---|---|---|
| Standard | 60 | 10,000 |
| Pro | 300 | 100,000 |
| Enterprise | Custom | Custom |
Contact support@wallbit.io to discuss Enterprise rate limits for high-volume use cases.
Rate Limit Headers
Every API response includes headers to help you track your rate limit status:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per minute |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | Unix timestamp when the limit resets |
Example Response Headers
Handling Rate Limits
When you exceed the rate limit, the API returns a429 Too Many Requests response:
Best Practices
Implement Exponential Backoff
Implement Exponential Backoff
When you receive a 429 response, wait before retrying. Use exponential backoff to gradually increase wait times:
Cache Responses
Cache Responses
Cache responses when possible to reduce API calls. Balance and asset data typically doesn’t change every second.
Batch Requests
Batch Requests
If you need multiple pieces of data, consider if there’s a single endpoint that can provide all the information you need instead of making multiple requests.
Rate Limit by Endpoint
Some endpoints may have different rate limits:| Endpoint Category | Limit |
|---|---|
| Read operations (GET) | Standard limit |
| Trade operations (POST /trades) | 10 per minute |
| Transfer operations (POST /operations) | 5 per minute |

