Understanding Throttling & Rate Limiting

Rate limiting

All tiers are subject to transactions-per-second (TPS) and monthly call limits.

If you receive a 429 Too Many Requests response:

• Read the Retry-After header to determine how long to wait before retrying.

• Wait for the specified period before making another request.

• Do not refresh or regenerate your JWT in response to a 429. A rate-limit response does not indicate that your authentication token has expired.

• Implement retry handling with appropriate backoff to prevent repeated requests from being rate limited.

Testing rate limiting in Sandbox

The Sandbox provides a 429 Test subscription specifically for testing your application's rate-limit handling.

When using this subscription:

• You are limited to 1 call every 60 seconds.

• A maximum of 10,000 calls per day is permitted.

• Use this subscription to test how your application handles 429 Too Many Requests responses and the Retry-After header.

Recommendation: Test your application's 429 handling in Sandbox before moving to production to ensure requests are paused and retried correctly without unnecessarily refreshing authentication credentials.