DatahyenaDatahyena

Rate limits

How Datahyena limits request rate, and how to back off cleanly.

Datahyena limits how many requests a workspace can make per minute. This is separate from credits: credits meter how many records you consume over time, while the rate limit caps how fast you send requests.

The limit

Requests are limited per workspace, per minute. The exact ceiling scales with your plan, higher plans get a higher rate. See pricing for the rate on each plan.

The limit is on request rate, not record volume. A single request that returns a full page of records counts as one request against the rate limit.

When you hit it

Over the limit, the API responds with 429 and the TOO_MANY_REQUESTS error code. The response includes a Retry-After header telling you how many seconds to wait before retrying.

{
  "success": false,
  "error": { "code": "TOO_MANY_REQUESTS", "message": "Workspace rate limit exceeded" }
}

Handling it

  • Honor Retry-After. Wait the number of seconds it specifies before the next request.
  • Back off exponentially on repeated 429s, with a little jitter, rather than retrying in a tight loop.
  • Spread bulk work out. If you are backfilling, page steadily instead of firing requests in parallel bursts.
  • A 429 is not charged, so a rate-limited request never costs credits.

See Errors for the full error-code list.

On this page