Revoke a Gateway Token
Revoke any token under a gateway, including an agentless one no agent endpoint can reach.
DELETE
Revoke a token under a gateway
Revokes a token that belongs to this gateway — either to one of its agents, or to
no agent at all. Revocation takes effect immediately; in-flight requests that
have already passed authentication complete.
This is the only way to revoke an agentless token. Pair it with
List gateway tokens when you find
a credential you cannot account for.
Returns
404 not_found if the token does not exist under this gateway, or is
already revoked. There is no POST counterpart: /v1 does not mint
gateway-level tokens.
Requires the delete capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.Authorizations
OAuth 2.1 authentication — recommended for new integrations. Access tokens
(kc_ prefix) are minted at the root-host token endpoint
https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>.
Public clients must use PKCE with the authorization_code grant; confidential
clients may use client_credentials. The first-party SDKs and the
knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.
Path Parameters
The AI gateway UUID.
The token UUID.