HTTP 401, ingestion

INGEST-001

Unknown ingest key.

What it means

The key is unrecognized or revoked. Keys are stored only as hashes, so a lost key cannot be recovered, only replaced.

What to do

Create a new key under Sources and update the recorder's configuration.

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/INGEST-001",
  "title": "Unknown ingest key.",
  "status": 401,
  "code": "INGEST-001",
  "trace_id": "01J8Z…"
}

Related codes

The endpoint your recorder sends to. The value-free gate lives here: a batch carrying real values is refused rather than stored, and the response names the offending path.

• INGEST-002Batch rejected: value-bearing payload.HTTP 422
• INGEST-003Batch exceeds the size limit.HTTP 413
• INGEST-004Ingest rate limit reached.HTTP 429

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