HTTP 422, ingestion

INGEST-002

Batch rejected: value-bearing payload.

What it means

The batch carried a real value where the contract permits only a typed placeholder. This is the value-free guarantee enforced as an input validator: the batch is refused rather than stored, and nothing from it is kept.

What to do

The response names the exact path that offended. Update the recorder, which strips values in your process before anything is sent, and resend.

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-002",
  "title": "Batch rejected: value-bearing payload.",
  "status": 422,
  "code": "INGEST-002",
  "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-001Unknown ingest key.HTTP 401
• 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.