Skip to content
ShiftGraph

HTTP 429, transport and validation

SYS-003

Rate limit reached.

What it means

Too many requests arrived in the window for this caller. Limits are applied per surface, so ingestion, sign-in, and the general API are counted separately and one cannot exhaust another.

What to do

Back off and retry, ideally with exponential backoff. If you are hitting this steadily rather than in bursts, tell us what you are building and we will look at the limit.

The response

Every failure arrives in this shape. The trace_id is worth keeping: it identifies the request in our logs and carries nothing about your data.

{
  "type": "https://shiftgraph.dev/errors/SYS-003",
  "title": "Rate limit reached.",
  "status": 429,
  "code": "SYS-003",
  "trace_id": "01J8Z…"
}

Related codes

Request shape, method, size, and rate. A 500 here is ours, and it carries a trace id we can look up.

The full error reference, or write to support@shiftgraph.dev with the trace id.