Idempotency & retries
Every write requires a UUID Idempotency-Key and JSON body, including DELETE and empty actions.
Verified behavior
- Generate the key once per logical operation
- On timeout/connection failure/500 retry the same method + path + payload + key
- Successful responses can replay for 24 hours
- Reuse with a different request returns 409
- Expired successful keys remain non-reusable
- Changed effective authority blocks historical replay
Write headers
Authorization: Bearer YOUR_OPERATIONAL_TOKEN Content-Type: application/json Accept: application/json Idempotency-Key: 6a97b0fc-e2b5-445d-abce-b8d91c61f262
Important
All example hostnames, IDs and tokens are placeholders. Test against staging first. The installed runtime services and exact OpenAPI contract remain authoritative for state transitions, nested schemas and additional permission checks.