Rate limits

How many requests your business can send per minute, and what to do when Gravv returns HTTP 429.

The API limits how many requests your business can make. The limit applies to requests made with an API key, on every endpoint.

The limit is 600 requests per minute (10 per second), with bursts of up to 50 requests. Gravv counts it per business, not per API key. Once you use up a burst, capacity comes back at 10 requests each second. Gravv rejects requests above that rate.

Each Gravv server counts the limit separately, so at times more requests than this may get through. Design for 600 requests per minute, and don't rely on more.

Handling rate limit errors

When you exceed the limit, Gravv returns HTTP 429 with no Retry-After header and this body:

{
  "data": null,
  "error": "Too many request"
}

Wait before you retry. Back off for about one second, with some random jitter, and double the wait if the retry also gets a 429.

Gravv does not run a rate-limited POST, but it stores the 429 response against the request's Idempotency-Key. Retry it with a new Idempotency-Key, or you get the same 429 back. See Idempotent requests.