missing_idempotency_key
HTTP 400Missing idempotency keyIngest API
What happened
A push arrived without an Idempotency-Key header. It is required, so that a retry can never apply a batch twice.
How to fix it
Send a key derived from the payload or from the job that produced it — the same value on every retry of the same batch. A fresh UUID per attempt is the one choice that defeats the purpose.
What you received
{
"type": "https://docs.sidelineexchange.com/errors/missing_idempotency_key",
"title": "Missing idempotency key",
"status": 400,
"detail": "…"
}Worth understanding
- 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.
- Batch — One push of up to 1,000 observations, recorded with what was accepted, what was rejected, and where the raw payload was stored.