Access Request Already Processed
Access Request Already Processed
Type URI: https://docs.rip.bet/errors/access_request_already_processed
What it means
An admin tried to approve or reject an access request that is no longer in
the pending state. Approve and reject are terminal transitions, and the
opposite action cannot be applied once one has been recorded. The HTTP
status is 409 Conflict.
When you might see this
- Approving an access request that has already been rejected.
- Rejecting an access request that has already been approved.
A repeat of the same action on an already-resolved request is a no-op and
returns 200, so this code is only emitted when the two terminal states
disagree.
How to resolve
- Re-fetch the request and check its current
statusbefore retrying; the response payload includes the latest decision. - If the prior decision was wrong, revoke it through the appropriate whitelist endpoint (for example, deleting the whitelist entry that an earlier approval created) rather than trying to flip the request itself.
- Surface the request's existing decision in the admin UI so reviewers do not double-action the same row.
Trading Errors
These are the most common user-actionable errors clients hit when placing or modifying orders, or when setting up an agent wallet for trading. Each entry lists the slug, status code, when it surfaces, and how to resolve it. Match on the slug (the final path segment of type), not the title or status alone — see Errors for the contract.
Access Revoked
Access Revoked