---
title: "Revoke Authorization Token"
method: POST
path: "/v1/authorization_tokens/{id}/revoke"
tags: ["Authorization Tokens"]
---

# Revoke Authorization Token

`POST /v1/authorization_tokens/{id}/revoke`

Revoke an unverified Authorization Token. Once revoked, the `code` can no longer be verified.
Tokens that have already been verified or expired cannot be revoked and will return status `412 Precondition Failed`.

## Path parameters

- `id` string, required

## Response `200`

The token was revoked

- DonorAuthorizationToken — A Donor Authorization Token is a single-use binding credential that ties a [Donor Account](/api/donor-accounts) to a verified identity exchange between DAFpay and the DAF. Tokens have two creation paths: - **DAF-Initiated Setup**: The DAF creates a Donor Account and then a token, surfaces the token's `code` to the donor via their portal, and the donor enters the `code` into DAFpay to approve their account. - **Donor-Initiated Verification**: After a donor submits a Grant Request without an approved Donor Account, DAFpay automatically creates a token and emails the `code` to the donor. The DAF later receives the `code` from the donor and calls [Verify Authorization Token](/api/authorization-tokens/verify) to approve the linked Donor Account. Tokens are single-use: once verified, the token's status becomes `verified` and the `code` cannot be used again.
  - `id` string, required — The unique identifier for this object.
  - `donor_account_id` string, required — The ID of the [Donor Account](/api/donor-accounts) this token is bound to.
  - `status` 'pending' | 'verified' | 'revoked' | 'expired', required — The status of a [Donor Authorization Token](/api/authorization-tokens). * `pending`: The token has been issued but not yet verified. * `verified`: The token has been verified and can no longer be used. * `revoked`: The token was explicitly revoked before being verified. * `expired`: The token's `expires_at` has passed and it can no longer be verified.
  - `code` string — The token's secret code value. <Warning> The `code` is **only returned in the response of [Create Authorization Token](/api/authorization-tokens/create)**. It is omitted from all other responses (Get, List). If the code is lost, [revoke](/api/authorization-tokens/revoke) the token and create a new one. </Warning> The format is a 12-character alphanumeric string designed to be easy for donors to read aloud or copy. Codes are not case-sensitive when verified.
  - `created_at` string, date-time, required — Time when the token was issued. Expressed in RFC 3339 format.
  - `expires_at` string, date-time, required — Time at which this token will expire and can no longer be verified. Defaults to 30 days after creation; configurable via the `expires_in` parameter on [Create Authorization Token](/api/authorization-tokens/create).
  - `verified_at` string, date-time — Time at which the token was verified. Only set when `status` is `verified`.
  - `revoked_at` string, date-time — Time at which the token was revoked. Only set when `status` is `revoked`.
  - `metadata` object — A map of arbitrary string keys and values to store information about the object.

## Other responses

- `400` — The request is invalid or contains invalid parameters
- `401` — Unauthorized. The request is missing the security (OAuth2 Bearer token) requirements and the server is unable to verify the identify of the caller.
- `403` — Access denied
- `404` — Resource Not Found
- `412` — Precondition Failed
- `500` — Internal Server Error

---

[API](https://skmtc.net/chariot-giving/apis/chariot-api.md) · [All operations](https://skmtc.net/chariot-giving/apis/chariot-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/chariot-giving/chariot-api/versions/dc28cadc066e/schema)