Skip to main content

Rate Limits

API rate limits are based on your subscription plan to ensure fair usage and system stability.

Handling Rate Limit Errors

When you exceed your rate limit, you’ll receive a 429 Too Many Requests response:

Rate Limit Tiers

Your rate limit allowance depends on your subscription plan:
Check your dashboard at aml.bitrace.io for your current rate limits and usage statistics.

Best Practices

1. Implement Exponential Backoff

Use exponential backoff when handling rate limit errors to avoid overwhelming the API:

2. Use Batching Efficiently

Batch endpoints consume multiple requests worth of quota:
  • 1 batch request with 10 addresses = 10 API calls
  • Plan your batching strategy based on your rate limit
Recommended approach:

3. Cache Responses

Implement caching to reduce redundant API calls:

Rate Limit by Endpoint

Different endpoints may have different rate limits:

Increasing Your Limits

Enterprise Options

For high-volume needs, contact us for:
  • Custom rate limits
  • SLA guarantees
  • Dedicated support
  • Priority processing

Optimization Tips

Before upgrading, try these optimizations:
  1. Implement caching - Reduce redundant calls
  2. Use batching - More efficient for multiple queries
  3. Optimize frequency - Don’t poll more than necessary
  4. Use webhooks - For real-time updates (if available)

Troubleshooting

Issue: Frequently Hitting Rate Limits

Solution: Implement exponential backoff and caching

Issue: 429 Errors Persist

Solution: Check that you’re respecting the Retry-After header

Issue: Rate Limit Too Low

Solution: Upgrade your plan or optimize your usage

Issue: Batch Requests Consuming Too Much Quota

Solution: Batch requests are billed per address. Consider batching only when necessary.

See Also