Country compliance
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.
Path parameters
The endpoints whose path names one of these take it as described here. An endpoint's own table lists a path parameter only when it describes it differently.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
campaignId | path | integer (int64) | required | Id of the campaign. |
Headers
The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
Ken-Version | header | string, one of: 2026-11-02, 1.1 | optional | 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy. |
X-Ken-Workspace-Id | header | integer (int64) | optional | 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. |
Get a campaign's compliance countries
/v1/campaigns/{campaignId}/compliancecampaign-compliance.get- Permission
- Campaigns view
- Rate limit
- 12,000 requests a minute per API key
multilingual_outreach feature on your workspace. Until it is on, calls answer 404.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.
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"Response 200
data is a CampaignCompliance.
Show the 2 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
Acknowledge a campaign's compliance countries
/v1/campaigns/{campaignId}/compliance/acknowledgementscampaign-compliance.acknowledge- Permission
- Campaigns edit
- Rate limit
- 4,800 requests a minute per API key
multilingual_outreach feature on your workspace. Until it is on, calls answer 404.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_failedwith detail coderequired:countriesis missing or empty.400 validation_failedwith detail codeunknown_country: a code is not a country Kenso knows.400 validation_failedwith detail codenot_required: the campaign has no contacts in that country, or its rules need no acknowledgement.404 not_found: the campaign does not exist in this workspace.
Requires Campaigns edit.
Request body
application/json, optional.
The countries to acknowledge.
| Field | Type | Required | Description |
|---|---|---|---|
countries | array of string | optional | 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. |
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"
]
}'Response 200
data is a CampaignCompliance.
Show the 2 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
More in Campaigns:CampaignsEmail sequencesLinkedIn sequencesSegment email sequencesSegment LinkedIn sequencesSequence variablesSequences with conditionsSequence importSegmentsLead listsShare linksClient approvalsSending capacityAuto-pausesCampaign languagesLocalized stepsText translationMarket packsCampaign imagesAll resources