idempotency_conflict (409)
idempotency_conflict
HTTP status: 409
Retryable: No. Retrying without changes will fail the same way.
The same Idempotency-Key was reused with a different request.
When it fires
For 24 hours after first use, an idempotency key is bound to the exact request body and the same canonical request path it was first sent with. Replaying with a different body or on a different canonical request path is rejected.
How to handle it
Pick a fresh idempotency key for the new request. Reuse the same key only when retrying the *exact* same operation after a network failure.
Example response
{
"error": {
"type": "https://docs-dev.autohost-dev.uk/api/errors/idempotency_conflict",
"code": "idempotency_conflict",
"message": "Idempotency-Key reused with a different request body",
"request_id": "req_01HEXAMPLE0000000000000000",
"doc_url": "https://docs-dev.autohost-dev.uk/api/errors/idempotency_conflict"
}
}