> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/campaigns/openapi.json](/docs/api/campaigns/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Campaigns: Count contacts by recipient provider

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Campaigns](/docs/api/campaigns.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Count contacts by recipient provider

`GET /v1/campaigns/{campaignId}/recipient-providers` - operationId `campaigns.list-recipient-providers`

| Permission | Rate limit |
| --- | --- |
| Campaigns view | 12,000 requests a minute per API key |

Counts the campaign's contacts that can still get an email under every mailbox provider and security gateway
Kenso tracks, including those with 0 contacts, most contacts first. Use it to plan sender routing rules.

Each contact is placed by the domain of the address Kenso emails. A contact counts once under its mailbox
provider and once under its security gateway. `pendingCount` counts contacts whose provider is still being
detected, and `noProviderCount` those with no known provider. At most 100,000 contacts are counted; past
that, `isPartial` is true.

Errors:

- `400 validation_failed`: the workspace does not have the sender routing feature (detail code
`feature_disabled`).
- `404 not_found`: the campaign does not exist in this workspace.

Requires Campaigns view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/campaigns/GET/v1/campaigns/%7BcampaignId%7D/recipient-providers)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `campaignId` | path | integer (int64) | yes | Id of the campaign. |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a `RecipientProviderCounts`.

| Field | Type | Description |
| --- | --- | --- |
| `providers` | array of RecipientProviderCount | Every mailbox provider and security gateway Kenso tracks, including those with 0 contacts, most contacts first. A contact counts once under its mailbox provider and once under its security gateway. |
| `pendingCount` | integer (int32) | Contacts whose provider is still being detected. |
| `noProviderCount` | integer (int32) | Contacts whose domain has no known provider, such as self-hosted mail or a domain with no MX record. |
| `isPartial` | boolean | True when more than 100,000 of the campaign's contacts can still get an email; the counts then cover the first 100,000 by id. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/campaigns/812/recipient-providers" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "providers": [
      {
        "slug": "google_workspace",
        "name": "Google Workspace",
        "kind": "mailbox_provider",
        "leadCount": 1104
      },
      {
        "slug": "microsoft_365",
        "name": "Microsoft 365",
        "kind": "mailbox_provider",
        "leadCount": 736
      },
      {
        "slug": "mimecast",
        "name": "Mimecast",
        "kind": "security_gateway",
        "leadCount": 87
      }
    ],
    "pendingCount": 64,
    "noProviderCount": 23,
    "isPartial": false
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### RecipientProviderCount

Contacts behind one mailbox provider or security gateway.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `slug` | string | no | Stable short id, such as `google_workspace` or `mimecast`. |
| `name` | string | no | Display name. |
| `kind` | string | no | Provider type: `mailbox_provider` or `security_gateway`. |
| `leadCount` | integer (int32) | no | Contacts that can still get an email and sit behind this provider. |
