Re-checks a CONNECTED apikey connector's stored credential against the…
Re-checks a CONNECTED apikey connector's stored credential against the provider, live (`hanzo connector verify`).
POST /v1/integrations/{provider}/verify
| Address | https://api.hanzo.ai/v1/integrations/{provider}/verify |
| Method | POST |
| Operation | post_integrations_by_provider_verify |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Re-checks a CONNECTED apikey connector's stored credential against the
provider, live (hanzo connector verify). Org-scoped (any member may check
status); the credential is read from KMS, verified, and NEVER returned or logged.
A verification failure is reported as {active:false}, not an error — the console/
CLI renders it. Only apikey providers support verify (OAuth tokens are checked at
use, not re-verified here).
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
provider | path | string | yes | Provider is the registry id of the connector — "slack", "github", "cloudflare". |
Response
| Status | Body | Meaning |
|---|---|---|
200 | verifyOut | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
account | body | string | — | Account is the account label the provider reported. |
active | body | boolean | — | Active is whether the stored credential verified live against the provider. |
externalId | body | string | — | ExternalID is the provider's account id. |
provider | body | string | — | Provider is the connector's registry id. |
reason | body | string | — | Reason is why the check failed. |
scopes | body | string[] | — | Scopes are the permissions the credential carries. |
Failure carries the platform error shape — see Errors.
Examples
hanzo integrations verify <provider>import { Configuration, IntegrationsApi } from 'hanzoai';
const api = new IntegrationsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIntegrationsByProviderVerify({ provider: 'provider' });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_by_provider_verify(provider='provider')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IntegrationsAPI.PostIntegrationsByProviderVerify(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_by_provider_verify(&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).postIntegrationsByProviderVerify();curl -X POST https://api.hanzo.ai/v1/integrations/<provider>/verify \
-H "Authorization: Bearer $HANZO_API_KEY"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"
}
}
}'How is this guide?