Connect user

Begins connecting the caller's own GitHub account: it answers the App's authorization page, carrying a state signed for this org and this person.

POST /v1/provider/github/user/connect

Addresshttps://api.hanzo.ai/v1/provider/github/user/connect
MethodPOST
Operationpost_provider_github_user_connect
AuthAuthorization: Bearer $HANZO_API_KEY

Begins connecting the caller's own GitHub account: it answers the App's authorization page, carrying a state signed for this org and this person. Every member may connect their own; it grants nothing the person does not already hold on GitHub.

Request

1 field, body application/json (required).

FieldInTypeRequiredDescription
returnbodystring—Return is the page the callback sends the person back to, with complete=github&grant=<id> (or error=github&reason=<why>) added to its query.

Response

StatusBodyMeaning
200provider.githubUserConnectOutok
defaultproblem-detailsrefused

200 body — 1 field.

FieldInTypeAlwaysDescription
authorizeUrlbodystring—AuthorizeURL is GitHub's authorization page for the App.

Failure carries the platform error shape — see Errors.

Examples

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

import { Configuration, ProviderApi } from 'hanzoai';

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProviderGithubUserConnect({ return: "<return>" });
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_connect(return="<return>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ProviderAPI.PostProviderGithubUserConnect(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_connect(&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).postProviderGithubUserConnect();
curl -X POST https://api.hanzo.ai/v1/provider/github/user/connect \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "return": "<return>"
     }'

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?