Verify provider
Re-checks a CONNECTED apikey connector's stored credential against the provider, live (`hanzo connector verify`).
POST /v1/provider/{provider}/verify
| Address | https://api.hanzo.ai/v1/provider/{provider}/verify |
| Method | POST |
| Operation | post_provider_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 | provider.verifyOut | ok |
default | problem-details | refused |
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 provider verify <provider>import { Configuration, ProviderApi } from 'hanzoai';
const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProviderByProviderVerify({ provider: 'provider' });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_by_provider_verify(provider='provider')cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.ProviderAPI.PostProviderByProviderVerify(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_by_provider_verify(&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).postProviderByProviderVerify();The method above is the one at the current release of the document. [email protected] (npm) was 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/<provider>/verify \
-H "Authorization: Bearer $HANZO_API_KEY"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?