Skip to main content
The Finrock API enforces rate limits on a per-minute, per-API-key basis. Rate limits apply globally across all endpoints associated with your API key. If your application exceeds the allowed number of requests within a one-minute window, the API returns an HTTP 429 Too Many Requests response. The limit automatically resets at the start of the next minute.
Rate limits are enforced per API key. If you need a higher limit for a production workload, contact support@finrock.io to request an increase.

Rate Limit Response Headers

Every API response includes rate limit headers so your application can proactively monitor its usage and back off before hitting the limit. Read these headers on every response:

Example Rate Limit Header Response

The following shows what the response headers look like when you call an endpoint with the -i flag in cURL to inspect them:
In this example, x-rate-limit-remaining: 999 shows there are 999 requests left in the current minute window, and the limit will reset at 2022-08-27T18:23:48Z.

Handling a 429 Response

When your application receives an HTTP 429, implement a back-off and retry strategy:
  1. Read the x-rate-limit-reset header to determine exactly when the window resets.
  2. Pause requests until that timestamp is reached.
  3. Resume sending requests at the start of the new window.
Do not retry a 429 response immediately in a tight loop — doing so will not succeed and will consume retries that could be used for legitimate requests. Always wait until the x-rate-limit-reset timestamp before resuming.