Complete user
Finishes connecting the caller's GitHub account: it takes the authorization the callback parked, trades it for the person's token, and seals it.
POST /v1/provider/github/user/complete
| Address | https://api.hanzo.ai/v1/provider/github/user/complete |
| Method | POST |
| Operation | post_provider_github_user_complete |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Finishes connecting the caller's GitHub account: it takes the authorization the callback parked, trades it for the person's token, and seals it. Only the person who started the flow can complete it — another person's grant id is simply not found — and a grant completes once.
Request
1 field, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
grant | body | string | — | Grant is the id the callback handed the console in its redirect. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | provider.githubUserOut | ok |
default | problem-details | refused |
200 body — 5 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
configured | body | boolean | — | Configured is whether this deployment holds the App's OAuth client. |
connected | body | boolean | — | Connected is whether the caller has connected their own GitHub account in this org. |
connectedAt | body | string | — | ConnectedAt is when the connection was made, RFC 3339 UTC. |
expiresAt | body | string | — | ExpiresAt is when the current access token expires, RFC 3339 UTC. |
login | body | string | — | Login is the GitHub account they connected. |
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.postProviderGithubUserComplete({ grant: "<grant>" });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_complete(grant="<grant>")cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.ProviderAPI.PostProviderGithubUserComplete(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_complete(&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).postProviderGithubUserComplete();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X POST https://api.hanzo.ai/v1/provider/github/user/complete \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"grant": "<grant>"
}'MCP declares no tool for provider — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?