HTTP 413, transport and validation

SYS-005

Request too large.

What it means

The request body is larger than this endpoint accepts. The limit exists so that a single request cannot occupy resources that belong to every other caller.

What to do

Split the work across several requests. If this is a capture rather than an API call, the recorder batches for you and is the supported path.

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-005",
  "title": "Request too large.",
  "status": 413,
  "code": "SYS-005",
  "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.

• SYS-001Invalid request.HTTP 400
• SYS-002Something went wrong on our side.HTTP 500
• SYS-003Rate limit reached.HTTP 429
• SYS-004Method not allowed.HTTP 405

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