Skip to main content
POST
RFC 7009 token revocation. Revoking a refresh token revokes the entire grant: every access and refresh token issued under it stops working. Access tokens can’t be revoked individually. Revoke the grant’s refresh token instead. Per RFC 7009, this endpoint always returns 200 with an empty body. Confidential clients must authenticate the same way they do at the token endpoint, using client_secret_basic, client_secret_post, or private_key_jwt. Public clients (none) send only client_id.

Body Parameters

string
required
The refresh token to revoke.
string
Required, except with client_secret_basic, where the Authorization header already carries it, and with private_key_jwt, where the assertion does.
string
Required for a confidential client using client_secret_post. Omit for public clients and for client_secret_basic (send the secret in the Authorization header instead).
string
Required with private_key_jwt. Must be urn:ietf:params:oauth:client-assertion-type:jwt-bearer.
string
Required with private_key_jwt: a newly signed JWT, as at the token endpoint.
string
Optional per RFC 7009. If set to "access_token", the request fails: access token revocation isn’t supported. Any other value (including "refresh_token") is accepted and ignored. Unknown hints don’t affect behavior.

Errors