invalid_batch
HTTP 400Invalid batchIngest API
What happened
Either the batch envelope does not conform to OYSS, or no observation inside it was valid. One bad observation among good ones does not cause this — it is rejected on its own and the batch still succeeds.
How to fix it
Read the errors array: each entry names the observation index and a JSON pointer to the field. Validating against the published schemas before sending turns this into a build-time error instead of a runtime one.
What you received
{
"type": "https://docs.sidelineexchange.com/errors/invalid_batch",
"title": "Invalid batch",
"status": 400,
"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.
- Problem document — The RFC 9457 shape every error uses: a stable type URI, a human detail, and for batches an errors array with the index and JSON pointer of each rejected observation.