Idempotency
Audience: Partner developer / integrator
Objective: Retry safely without duplicate bookings or side effects.
Why it matters
Mobile networks fail. Clients retry. Without idempotency keys, you can double-create reservations or posts.
Practice
- Send a unique idempotency key on creating mutations when the API documents support for it.
- Retry the same key for the same logical operation.
- Do not reuse a key for a different payload.
- On loyalty earn and similar server paths, prefer server idempotency - still use client keys where documented.
Related
- OpenAPI map
- Inspect current headers/fields in
/api/v1/openapi(source of truth).