Revoke an Issued Token

DELETE

/oauth-tokens/{token}

Last modified:2026-08-12 21:59:30

OperationId:revokeOauthToken

Revokes a single token. The revocation is replicated across the cluster, so the token stops validating everywhere and not merely on the server that handled this request.

Revoking an access token does not revoke its paired refresh token — refresh tokens are separate rows. List both with GET /oauth-tokens?user-id={uid} and revoke each.

Requires full Super User (Super User Read Only is refused).

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Responses

🟢202Accepted

Delete accepted. No body — the removal is published to the cluster.

This response does not have a body.

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/oauth-tokens/' \
--header 'Authorization: Bearer <token>'

Response Example

401 - No / expired token

{
    "code": 401,
    "message": "Unauthorized"
}

Modified at 2026-08-12 21:59:30

Read an Issued Token

Inbox