CLIENT_SECRET_REVOKE_CONFLICT
409invalid_requestThe secret you asked to revoke was already replaced.
Cause
A concurrent rotation swapped in a new secret, so the revoke targeted a value that is no longer live.
How to fix it
Re-read the current secret and reissue the revoke against it.
Example response
409 CLIENT_SECRET_REVOKE_CONFLICT
JSON
{
"error_code": "CLIENT_SECRET_REVOKE_CONFLICT",
"error_type": "invalid_request",
"error_message": "The secret you asked to revoke was already replaced.",
"hint": "Re-read the current secret and reissue the revoke against it.",
"docs_url": "https://docs.billerapi.com/errors/CLIENT_SECRET_REVOKE_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_REVOKE_CONFLICT
Was this page helpful?