CLIENT_SECRET_ROTATION_CONFLICT
409invalid_requestA concurrent rotate or revoke won the race.
Cause
Another writer changed the secret first, so this rotation was not applied and no plaintext was issued.
How to fix it
Re-read the current secret state, and rotate again only if you still need to.
Example response
409 CLIENT_SECRET_ROTATION_CONFLICT
JSON
{
"error_code": "CLIENT_SECRET_ROTATION_CONFLICT",
"error_type": "invalid_request",
"error_message": "A concurrent rotate or revoke won the race.",
"hint": "Re-read the current secret state, and rotate again only if you still need to.",
"docs_url": "https://docs.billerapi.com/errors/CLIENT_SECRET_ROTATION_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_SECRET_ROTATION_CONFLICT
Was this page helpful?