Is the direct intake path: a customer-held token/setup-token (Verify) or an…

Is the direct intake path: a customer-held token/setup-token (Verify) or an externally obtained OAuth bundle from the CLI's local PKCE (Adopt).

POST /v1/integrations/connectors/{provider}/credential

Integrations → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/integrations/connectors/{provider}/credential`
Method	`POST`
Operation	`post_integrations_connectors_by_provider_credential`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Is the direct intake path: a customer-held token/setup-token (Verify) or an externally obtained OAuth bundle from the CLI's local PKCE (Adopt). ALWAYS verify-before-store: a bad credential is refused and NOTHING is persisted (connectByCredential's fail-closed order).

Request

9 fields, body application/json (required).

Field	In	Type	Required	Description
`provider`	path	string	yes	Provider is the user-scoped provider's registry id, from the path.
`accountId`	body	string	—	AccountID scopes the credential where the provider's Verify needs one.
`label`	body	string	—	Label names this connection; empty means "default".
`oauth`	body	oauthBundleIn	—
`oauth.access`	body	string	—	Access is the access token.
`oauth.account`	body	string	—	Account is the account label the flow reported; sanitized on ingest.
`oauth.refresh`	body	string	—	Refresh is the refresh token.
`provider`	body	string	—	Provider is the user-scoped provider's registry id, from the path.
`token`	body	string	—	Token is the customer-held credential for the Verify path.

Response

Status	Body	Meaning
`200`	credentialOut	ok

200 body — 10 fields.

Field	In	Type	Always	Description
`connected`	body	boolean	—	Connected is always true — a failed verification is a 400 and stores nothing.
`connector`	body	connView	—
`connector.account`	body	string	—	Account is the provider's label for the connected account.
`connector.connectedAt`	body	string	—	ConnectedAt is when the connector was last (re)established, RFC 3339 UTC.
`connector.expiresAt`	body	string	—	ExpiresAt is when the access token expires, RFC 3339 UTC; empty for a non-expiring credential.
`connector.externalId`	body	string	—	ExternalID is the provider's own id for that account.
`connector.id`	body	string	—	ID is provider + ":" + label — what every other connector route addresses.
`connector.label`	body	string	—	Label is the caller's name for this connection ("default", "work").
`connector.provider`	body	string	—	Provider is the user-scoped provider's registry id.
`connector.scopes`	body	string[]	—	Scopes are the permissions the credential carries.

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, IntegrationsApi } from 'hanzoai';

const api = new IntegrationsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIntegrationsConnectorsByProviderCredential({ provider: 'provider', accountId: "<accountId>", label: "<label>" });

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IntegrationsApi(client).post_integrations_connectors_by_provider_credential(provider='provider', account_id="<accountId>", label="<label>")

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

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

use hanzo_cloud::apis::{configuration::Configuration, integrations_api};

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

let result = integrations_api::post_integrations_connectors_by_provider_credential(&cfg, Default::default()).await?;

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

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

var result = new IntegrationsApi(client).postIntegrationsConnectorsByProviderCredential();

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/integrations/connectors/<provider>/credential \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "accountId": "<accountId>",
       "label": "<label>"
     }'

The door reaches integrations through the integrations tool, which names its 45 operations with its own verbs — this one among them, under a name only the door 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_connectors"
         }
       }
     }'

Integrations API · All Hanzo APIs · Interactive reference

Is the direct intake path: a customer-held token/setup-token (Verify) or an…

Request

Response

Examples

On this page