> 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: Get a campaign's LinkedIn settings

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

## Get a campaign's LinkedIn settings

`GET /v1/campaigns/{campaignId}/linkedin-settings` - operationId `campaigns.get-linkedin-settings`

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

Returns how the campaign uses LinkedIn alongside email: whether LinkedIn steps run, how the two channels combine,
how long to wait on connection requests, and which replies stop which channel.

Errors:

- `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/linkedin-settings)

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

| Field | Type | Description |
| --- | --- | --- |
| `isEnabled` | boolean | True when the campaign runs LinkedIn steps. |
| `channelPolicy` | string | How LinkedIn and email combine: `linkedin_only` sends no email, `linkedin_first_email_fallback` emails a contact only once LinkedIn cannot reach them, `email_first_linkedin_reinforce` starts LinkedIn after the contact's email sequence has started, and `parallel` runs both independently. |
| `notAcceptedAfterDays` | integer (int32) | Days to wait for a connection request to be accepted, from 1 to 90. |
| `conditionWaitDays` | integer (int32) | Days a step waits for its condition before it is skipped, from 1 to 60. |
| `isWithdrawEnabled` | boolean | True withdraws a connection request that was not accepted within `notAcceptedAfterDays`. |
| `stopLinkedInOnEmailReply` | boolean | True stops a contact's LinkedIn steps when they reply by email. |
| `stopEmailOnLinkedInReply` | boolean | True stops a contact's emails when they reply on LinkedIn. |
| `stopSequenceForCompanyOnReply` | boolean | True stops the sequence for every contact at the same company when one of them replies. It is the same setting as the campaign's `stopCompanyOnReply`. |
| `stopAllChannelsOnReply` | boolean | True stops every channel when the contact replies on any channel, also after their LinkedIn steps finished: a LinkedIn reply then still stops the emails (with `stopEmailOnLinkedInReply`). New campaigns start with true. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/campaigns/812/linkedin-settings" \
  -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": {
    "isEnabled": true,
    "channelPolicy": "email_first_linkedin_reinforce",
    "notAcceptedAfterDays": 21,
    "conditionWaitDays": 14,
    "isWithdrawEnabled": true,
    "stopLinkedInOnEmailReply": true,
    "stopEmailOnLinkedInReply": true,
    "stopSequenceForCompanyOnReply": true,
    "stopAllChannelsOnReply": true
  }
}
```
