Sideline Exchange/
Dashboard →

Errors

payload_too_large

HTTP 413Payload too largeIngest API

What happened

The body exceeds the limit for the endpoint, or a batch carries more than 1,000 observations.

How to fix it

Split the work into several batches, each with its own idempotency key. Batches are cheap; a 40 MB one is not.

What you received
{
  "type": "https://docs.sidelineexchange.com/errors/payload_too_large",
  "title": "Payload too large",
  "status": 413,
  "detail": "…"
}

Worth understanding

  • Batch — One push of up to 1,000 observations, recorded with what was accepted, what was rejected, and where the raw payload was stored.
  • Idempotency key — A caller-chosen string that makes a retry safe: replaying a batch with the same key returns the original receipt instead of applying twice.