Rate Limits
Understanding how TaxStreem throttles requests to ensure platform stability.
We employ throttling mechanisms natively across all API endpoints to guarantee fair ecosystem usage and maintain lightning-fast response times. When you exceed the allocated capacity, our gateway will respond with a 429 Too Many Requests status code.
⏱️ Standard Limits
Rate limits are uniquely bound to your x-api-key credential array and depend entirely on the environment execution mode:
| Environment | Requests per Second (RPS) | Burst Maximum |
|---|---|---|
| Sandbox | 5 RPS | 10 concurrent |
| Production | 50 RPS | 100 concurrent |
📊 Response Headers
Every successful HTTP response explicitly returns metadata headers regarding your current limits. Your application should utilize these dynamically to safely meter outbound loops.
| Header Name | Description |
|---|---|
| X-RateLimit-Limit | The maximum number of requests you're permitted to make per second. |
| X-RateLimit-Remaining | The number of requests remaining in the current window block. |
| X-RateLimit-Reset | Uniquely formatted UNIX timestamp evaluating when the throttle window fully resets. |
🛠️ Handling 429 Errors
If your application spikes and hits the ceiling resulting in a 429 response, you should safely queue and retry utilizing standard algorithms:
/batch-filing endpoints where a single request can encompass 500 ledgers.💡 Additional Notes
enterprise@taxstreem.com for routing.