Hanzo
OpenapiIntegrations

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

Addresshttps://api.hanzo.ai/v1/integrations/{provider}/verify
MethodPOST
Operationpost_integrations_by_provider_verify
AuthAuthorization: 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.

FieldInTypeRequiredDescription
providerpathstringyesProvider is the registry id of the connector — "slack", "github", "cloudflare".

Response

StatusBodyMeaning
200verifyOutok

200 body — 6 fields.

FieldInTypeAlwaysDescription
accountbodystringAccount is the account label the provider reported.
activebodybooleanActive is whether the stored credential verified live against the provider.
externalIdbodystringExternalID is the provider's account id.
providerbodystringProvider is the connector's registry id.
reasonbodystringReason is why the check failed.
scopesbodystring[]Scopes are the permissions the credential carries.

Failure carries the platform error shape — see Errors.

Examples

hanzo integrations verify <provider>

Integrations API · All Hanzo APIs · Interactive reference

How is this guide?

On this page