Revoke oauth

Retires a token before it expires — what you call when someone signs out or a credential may have leaked.

POST /v1/iam/oauth/revoke

Addresshttps://api.hanzo.ai/v1/iam/oauth/revoke
MethodPOST
Operationpost_iam_oauth_revoke
AuthAuthorization: Bearer $HANZO_API_KEY

Retires a token before it expires — what you call when someone signs out or a credential may have leaked.

Revoking an access token kills that token. Revoking a REFRESH token kills the whole chain it belongs to, so no further access tokens can be minted from it and every token already minted from it dies with it.

A token that is not yours, or that never existed, answers success and does nothing — so the endpoint cannot be used to discover which tokens are real.

PUBLIC clients revoke too, and must: sign-out is the only control a long-lived refresh token has (RFC 7009 §2.1 — a public client identifies itself with client_id). A browser app or CLI is a public PKCE client and holds no secret, and that includes the public half of a registration that keeps a secret for a backend path, so requiring one here would leave signing out as a local delete — forgetting a credential that stays spendable for the rest of its lifetime.

Widening authentication does not widen authority. The caller must still POSSESS the token — and possession already permits USE, of which revocation is the strict opposite — and the row must belong to the client that presents it. A caller that did not prove the registration's secret revokes only a grant that was itself established without it, so a public client_id buys the ability to destroy exactly what its holder could otherwise spend.

Request

The document declares no body for POST /v1/iam/oauth/revoke. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for post_iam_oauth_revoke, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo iam oauth revoke
import { Configuration, IamApi } from 'hanzoai';

const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIamOauthRevoke();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IamApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IamApi(client).post_iam_oauth_revoke()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.IamAPI.PostIamOauthRevoke(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, iam_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = iam_api::post_iam_oauth_revoke(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IamApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new IamApi(client).postIamOauthRevoke();
curl -X POST https://api.hanzo.ai/v1/iam/oauth/revoke \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches iam through the iam tool, which names its 44 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_iam_applications"
         }
       }
     }'

IAM API · All Hanzo APIs · Interactive reference

Was this page useful?