# Verify provider

URL: https://docs.hanzo.ai/docs/openapi/provider/post-provider-by-provider-verify

> Re-checks a CONNECTED apikey connector's stored credential against the provider, live (`hanzo connector verify`).

`POST /v1/provider/{provider}/verify`

> [Provider →](https://docs.hanzo.ai/docs/openapi/provider) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                                      |
| ------------- | ---------------------------------------------------- |
| **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](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo provider verify <provider>
```

**SDK**

**.ts**

```ts
import { Configuration, ProviderApi } from 'hanzoai';

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProviderByProviderVerify({ provider: 'provider' });
```

**.py**

```python
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')
```

**.go**

```go
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
}
```

**.rs**

```rust
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?;
```

**.java**

```java
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();
```

**HTTP**

```bash
curl -X POST https://api.hanzo.ai/v1/provider/<provider>/verify \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **provider** through the `provider` tool, which names its 38 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them:

```bash
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_connections"
         }
       }
     }'
```

---

[Provider API](https://docs.hanzo.ai/docs/openapi/provider) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)