Campaign languages
A campaign can send each contact its email and LinkedIn steps in the contact's own language, called the outreach language. Read a campaign's language settings, the languages it can turn on, and how many contacts have each outreach language. Change the settings with PATCH /v1/campaigns/{campaignId}, and write the translated steps with the campaign localizations calls.
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 languages
/v1/campaigns/{campaignId}/languagescampaign-languages.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.Returns the campaign's language settings, the market packs it can turn on, and its contacts counted per outreach language. Use it to choose which languages to turn on before you generate localizations.
The five settings have the same values as on the campaign: sourceLanguage, languageMode, enabledLanguages, formalityOverrides and languageFallback. Change them with PATCH /v1/campaigns/{campaignId}. available lists every market pack the campaign can turn on, by locale. mix counts the campaign's contacts per outreach language, most contacts first, and unresolved counts the contacts with no outreach language yet. Kenso counts contacts that are not deleted and not marked do not contact.
Errors:
404 not_found: the campaign does not exist in this workspace.
Requires Campaigns view.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
campaignId | path | integer (int64) | required | Id of the campaign. |
curl -X GET "https://api.ken.so/v1/campaigns/812/languages" \
-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 CampaignLanguages.
Show the 8 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-pausesLocalized stepsText translationMarket packsCountry complianceCampaign imagesAll resources