Skip to main content

Rate Limits

The Wallbit API implements rate limiting to ensure fair usage and maintain service stability for all users.

Current Limits

Contact [email protected] 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:

Example Response Headers

Handling Rate Limits

When you exceed the rate limit, the API returns a 429 Too Many Requests response:

Best Practices

When you receive a 429 response, wait before retrying. Use exponential backoff to gradually increase wait times:
Cache responses when possible to reduce API calls. Balance and asset data typically doesn’t change every second.
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:
Trade and transfer operations have lower limits to prevent accidental rapid-fire transactions.