Disconnect user

Forgets the caller's GitHub connection in this org: the token is revoked at GitHub, and the sealed secrets and the row go.

POST /v1/provider/github/user/disconnect

Provider → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/provider/github/user/disconnect`
Method	`POST`
Operation	`post_provider_github_user_disconnect`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Forgets the caller's GitHub connection in this org: the token is revoked at GitHub, and the sealed secrets and the row go. It says whether GitHub confirmed the revocation rather than reporting a success it did not see. Disconnecting what is not connected succeeds.

Request

The document declares no body for POST /v1/provider/github/user/disconnect. 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_provider_github_user_disconnect, which answers from the running route.

Response

Status	Body	Meaning
`200`	provider.githubUserDisconnectOut	ok
`default`	problem-details	refused

200 body — 2 fields.

Field	In	Type	Always	Description
`disconnected`	body	boolean	—	Disconnected is always true: the sealed token and the connection are gone from this deployment.
`revoked`	body	boolean	—	Revoked is whether GitHub confirmed the token is dead.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

.ts

.py

.go

.rs

.java

import { Configuration, ProviderApi } from 'hanzoai';

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProviderGithubUserDisconnect();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProviderApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProviderApi(client).post_provider_github_user_disconnect()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ProviderAPI.PostProviderGithubUserDisconnect(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, provider_api};

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

let result = provider_api::post_provider_github_user_disconnect(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProviderApi;

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

var result = new ProviderApi(client).postProviderGithubUserDisconnect();

curl -X POST https://api.hanzo.ai/v1/provider/github/user/disconnect \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches provider through the provider tool, which names its 38 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_connections"
         }
       }
     }'

Provider API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousConnect user NextCreate webhook — POST /v1/provider/github/webhook