Request Conflicts With Revoked Identifier

Type URI: https://docs.rip.bet/errors/request_conflicts_with_revoked_identifier

Deprecated. This error code is preserved for clients that still match on the slug, but it is not emitted by the current API. The equivalent condition is now reported as identifier_revoked.

What it means

A previous version of the admin API returned this code when an approval operation would have conflicted with a revoked wallet or email. The status was 409 Conflict. The handling logic has been folded into the identifier_revoked flow on the whitelist endpoint, and approve/reject flows now use access_request_already_processed for state-conflict cases.

When you might see this

You should not see this code from a current backend. If a client receives it, it is either:

• Replaying a recorded response from an older deployment, or
• Talking to a non-production environment that still pins an old API build.

How to resolve

• Match on the new slug identifier_revoked going forward; treat both slugs as equivalent until older clients are retired.
• If you are seeing this from a live RIPBET environment, capture the full response (including instance and any request ID) and report it to support — it indicates the deployment is behind the documented contract.