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

# Country compliance

> **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.

Some countries restrict cold email to business contacts, such as Germany or Spain. When a campaign has contacts in one of them, a member acknowledges that country's cold email rules once before the campaign launches. Read the countries a campaign needs acknowledged, then acknowledge them. Until every listed country is acknowledged, launching the campaign answers `409 acknowledgement_required`.

Campaigns. 2 endpoints under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/campaign-compliance/openapi.json](/docs/api/campaign-compliance/openapi.json).

- `GET /v1/campaigns/{campaignId}/compliance` - Get a campaign's compliance countries (`campaign-compliance.get`): [/docs/api/campaign-compliance/get.md](/docs/api/campaign-compliance/get.md)
- `POST /v1/campaigns/{campaignId}/compliance/acknowledgements` - Acknowledge a campaign's compliance countries (`campaign-compliance.acknowledge`): [/docs/api/campaign-compliance/acknowledge.md](/docs/api/campaign-compliance/acknowledge.md)

## Get a campaign's compliance countries

`GET /v1/campaigns/{campaignId}/compliance` - operationId `campaign-compliance.get`

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

Lists each country whose cold email rules a member must acknowledge before the campaign launches. Call it before
launch to show which rules to read.

A country appears when its rules need an acknowledgement and the campaign has at least one contact there. Kenso
counts contacts that are not deleted and not marked do not contact, and lists the country with the most contacts
first. Each country carries a short note on its rules and links to the public sources. An empty
`countries` list means the campaign needs no acknowledgement.

`acknowledgementRequired` is true while any listed country has no acknowledgement. While it is true,
`POST /v1/campaigns/{campaignId}/launch` answers `409 acknowledgement_required`, and
`GET /v1/campaigns/{campaignId}/launch-readiness` lists `acknowledgement_required`.

Errors:

- `404 not_found`: the campaign does not exist in this workspace.

Requires Campaigns view.

Needs the `multilingual_outreach` feature on your workspace. Until it is on, calls answer 404.

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

### 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 `CampaignCompliance`.

| Field | Type | Description |
| --- | --- | --- |
| `acknowledgementRequired` | boolean | True while any country in `countries` has no acknowledgement. While it is true, launching the campaign answers `409 acknowledgement_required`. |
| `countries` | array of CampaignComplianceCountry | Each country whose rules need an acknowledgement and where the campaign has contacts, most contacts first. Empty when the campaign needs no acknowledgement. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/campaigns/812/compliance" \
  -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": {
    "acknowledgementRequired": true,
    "countries": [
      {
        "iso2": "ES",
        "name": "Spain",
        "regime": "string",
        "note": "string",
        "sources": [
          "string"
        ],
        "contactCount": 1,
        "acknowledgedAt": "2026-09-23T15:02:11Z",
        "acknowledgedByUserId": 812
      }
    ]
  }
}
```

## Acknowledge a campaign's compliance countries

`POST /v1/campaigns/{campaignId}/compliance/acknowledgements` - operationId `campaign-compliance.acknowledge`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 4,800 requests a minute per API key |

Records that the caller read the cold email rules of one or more countries the campaign lists, so the campaign can
launch to them. Call it after `GET /v1/campaigns/{campaignId}/compliance` shows countries with no
acknowledgement.

Send `countries` with the ISO 3166-1 alpha-2 codes to acknowledge, such as `["ES", "DE"]`, in any
letter case. Kenso stores the caller and the time for each country. A country that already has an acknowledgement
keeps the first one, so repeating the call changes nothing. If any code is refused, Kenso records none of them.
The response is the campaign's compliance after the write, in the same shape as
`GET /v1/campaigns/{campaignId}/compliance`.

Errors:

- `400 validation_failed` with detail code `required`: `countries` is missing or empty.
- `400 validation_failed` with detail code `unknown_country`: a code is not a country Kenso knows.
- `400 validation_failed` with detail code `not_required`: the campaign has no contacts in that country, or its rules need no acknowledgement.
- `403 forbidden`: the caller is a workspace key. An acknowledgement records the member who read the rules,
and a workspace key is not a person.
- `404 not_found`: the campaign does not exist in this workspace.

Requires Campaigns edit.

Needs the `multilingual_outreach` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/campaign-compliance/POST/v1/campaigns/%7BcampaignId%7D/compliance/acknowledgements)

### 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`. |

### Request body

`application/json`, optional.

The countries to acknowledge.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `countries` | array of string | no | ISO 3166-1 alpha-2 codes of countries that `GET /v1/campaigns/{campaignId}/compliance` lists for this campaign, such as `ES`, in any letter case. At least one. |

### Response 200

`data` is a `CampaignCompliance`.

| Field | Type | Description |
| --- | --- | --- |
| `acknowledgementRequired` | boolean | True while any country in `countries` has no acknowledgement. While it is true, launching the campaign answers `409 acknowledgement_required`. |
| `countries` | array of CampaignComplianceCountry | Each country whose rules need an acknowledgement and where the campaign has contacts, most contacts first. Empty when the campaign needs no acknowledgement. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/campaigns/812/compliance/acknowledgements" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "countries": [
    "ES"
  ]
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "acknowledgementRequired": true,
    "countries": [
      {
        "iso2": "ES",
        "name": "Spain",
        "regime": "string",
        "note": "string",
        "sources": [
          "string"
        ],
        "contactCount": 1,
        "acknowledgedAt": "2026-09-23T15:02:11Z",
        "acknowledgedByUserId": 812
      }
    ]
  }
}
```

## Types

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

### CampaignComplianceCountry

One country whose cold email rules a member must acknowledge before the campaign launches.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `iso2` | string | no | ISO 3166-1 alpha-2 code of the country, uppercase, such as `ES`. |
| `name` | string | no | English name of the country, such as `Spain`. |
| `regime` | string | no | How the country's law treats cold email to business contacts: `opt_out` (allowed when the sender identifies itself and honors opt-outs), `consent` (needs prior consent, apart from narrow exceptions) or `unresolved` (the law does not settle it). |
| `note` | string | no | A short summary of the country's rule. It ends with "Not legal advice." |
| `sources` | array of string | no | Links to the public pages the note is based on. |
| `contactCount` | integer (int32) | no | Number of the campaign's contacts in this country. Kenso counts contacts that are not deleted and not marked do not contact. |
| `acknowledgedAt` | string (date-time) | no | When a member acknowledged the country's rules for this campaign, in UTC. Omitted until someone does. |
| `acknowledgedByUserId` | integer (int64) | no | Id of the member who acknowledged the rules. Omitted until someone does, and when the acknowledgement came from an API key that is not tied to a member. |

All resources: [/docs.md](/docs.md).
