Overview
TXCloud implements rate limiting to ensure fair usage and maintain API stability. Rate limits vary by plan and endpoint type.Rate Limit Tiers
Burst limit is the maximum number of concurrent requests allowed.
Endpoint-Specific Limits
Some endpoints have additional limits:Rate Limit Headers
Every API response includes rate limit information in the headers:Handling Rate Limits
When you exceed the rate limit, you’ll receive a429 Too Many Requests response:
Implementing Retry Logic
Best Practices
Implement Exponential Backoff
Implement Exponential Backoff
Use exponential backoff for retries:
Use Caching
Use Caching
Cache responses when possible to reduce API calls:
- Cache verification results by ID
- Cache user risk profiles
- Cache configuration data
Batch Requests
Batch Requests
Use batch endpoints when available:
Monitor Usage
Monitor Usage
Track your API usage in the dashboard to predict rate limit issues.
Increasing Your Limits
Need higher rate limits? Options include:- Upgrade your plan — Higher plans have higher limits
- Request a limit increase — Contact sales for custom limits
- Optimize your integration — Reduce unnecessary calls
Contact Sales
Discuss custom rate limits for enterprise needs