Rate Limiting

The Routable API employs rate limiting against bursts of incoming traffic to help maximize its stability. Customers who send too many requests in quick succession may see 429 Too Many Requests errors returned.

• For most endpoints, Routable allows 600 requests per minute.
• For endpoints that perform a great deal of work, such as our Create a Payable endpoint, Routable allows 100 requests per minute.

You can learn about your current rate limit status by inspecting the Rate-Limit and RateLimit-Policy headers in any Routable API response. A brief summary of each follows. See the Draft RFC for these headers for details about their formatting.

Rate-Limit

The Rate-Limit header is expressed in the format:
"fetch";r=0;t=60;pk=:8c581d79-bb84-4bc1-b1c5-8c073264a569:

There are two policies listed: fetch for most GET endpoints, and change for endpoints that modify data like POST and PUT. For each policy:

• The r parameter is the rate - how many more calls you can make in the given window. Once this number reaches 0, your requests will fail with a 429 Too Many Requests response.
• The t parameter is the time - how many seconds before the window resets and more calls can be made.

RateLimit-Policy

The RateLimit-Policy header is expressed in the format:
"fetch";q=600;w=60;pk=:8c581d79-bb84-4bc1-b1c5-8c073264a569:

There are two policies listed: fetch for most GET endpoints, and change for endpoints that modify data like POST and PUT. For each policy:

• The q parameter is the quota - how many requests can be made during the given window.
• The w parameter is the window - how long (in seconds) before a new quota of requests is permitted.