Get a mandate revocation
Retrieves a single revocation by ID.
Authorizations
A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.
Path Parameters
The unique identifier of the mandate.
The ID of the mandate, a UUID prefixed by mandate_.
^mandate_[a-f0-9\-]{36}$"mandate_82c879c1-84e1-44ed-a8c2-1ac239cf09ad"
The unique identifier of the revocation.
The ID of a revocation, a UUID prefixed by revocation_.
^revocation_[a-f0-9\-]{36}$"revocation_9d2e7c14-3b8a-4f21-9c66-2a1e5d7b8f03"
Response
Successfully retrieved mandate revocation.
A record of a wallet revocation: the customer removing the mandate's spending allowance on-chain (see onchainTransactions). While it is confirming, the mandate's status is revocation_pending; on success it becomes revocation_succeeded and the mandate's revokedAt is set, and on failure it becomes revocation_failed. This applies regardless of whether the mandate was previously canceled: a revocation on an already-canceled mandate still moves status through the revocation_* values and sets revokedAt.
To check whether the spending allowance is still active, read the mandate: revokedAt is set once the allowance has been removed.
The unique identifier of the revocation.
^revocation_[a-f0-9\-]{36}$"revocation_9d2e7c14-3b8a-4f21-9c66-2a1e5d7b8f03"
The unique identifier of the mandate this revocation applies to.
^mandate_[a-f0-9\-]{36}$"mandate_82c879c1-84e1-44ed-a8c2-1ac239cf09ad"
The current status of the revocation attempt.
pending, succeeded, failed "succeeded"
The UTC ISO 8601 timestamp at which the revocation was created.
"2026-08-21T14:10:00.000Z"
The UTC ISO 8601 timestamp at which the revocation was last updated.
"2026-08-21T14:12:00.000Z"
Network transactions that remove the spending allowance on-chain. Empty until the revocation has been submitted to the network.
Details of why the revocation failed. Only present when status is failed.
Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.