CLIENT_FEEDBACK_IDEMPOTENCY_CONFLICT
409invalid_requestThe idempotency key was reused with different content.
Cause
The key is bound to the first payload it saw; a different payload under the same key is a client bug, not a retry.
How to fix it
Retry byte-identically to replay the original result, or mint a fresh idempotency_key for genuinely new feedback.
Example response
409 CLIENT_FEEDBACK_IDEMPOTENCY_CONFLICT
JSON
{
"error_code": "CLIENT_FEEDBACK_IDEMPOTENCY_CONFLICT",
"error_type": "invalid_request",
"error_message": "The idempotency key was reused with different content.",
"hint": "Retry byte-identically to replay the original result, or mint a fresh idempotency_key for genuinely new feedback.",
"docs_url": "https://docs.billerapi.com/errors/CLIENT_FEEDBACK_IDEMPOTENCY_CONFLICT",
"request_id": "d94f5e2a-8c3b-4f1e-9a7d-6b2c1e0f8a34"
}Related
- Error handling — the error envelope shape and how to parse it
- Error code reference — every stable error code
Canonical docs URL: https://docs.billerapi.com/errors/CLIENT_FEEDBACK_IDEMPOTENCY_CONFLICT
Was this page helpful?