Access Revoked

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

What it means

The authenticated identity has been explicitly blocked from the API. Authentication itself succeeded — the JWT is valid — but an admin has revoked this wallet or email. The HTTP status is 403 Forbidden.

This is distinct from not_allowlisted (also 403), which is returned when an identity is merely waitlisted and has never been approved.

When you might see this

• Any guarded REST endpoint behind the allowlist guard, for example POST /v1/orders or any admin route.
• Upgrading to the WebSocket aggregator with a revoked identity.

How to resolve

• Treat this as a terminal decision for the current identity. Sign the user out and stop retrying with the same credentials.
• If the user believes the revocation is incorrect, direct them to contact support so an admin can review the case. Do not poll for recovery; an explicit admin action is required to restore access.
• A revoked user may submit a fresh access request via POST /v1/access-requests, which is the one allowlist-bypassing path available to them.