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

# LinkedIn accounts: Start a LinkedIn connect session

> **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 [LinkedIn accounts](/docs/api/linkedin-accounts.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Start a LinkedIn connect session

`POST /v1/linkedin-accounts/connect-sessions` - operationId `linkedin-accounts.create-connect-session`

| Permission | Credits | Rate limit |
| --- | --- | --- |
| Any workspace member, Network members included | 1,500 credits per LinkedIn account a month (`linkedin_account_monthly`) | 10 requests a minute per API key |

Returns a hosted link where the member signs in to LinkedIn to connect a new account or reconnect an existing
one. Open `url` within one hour.

Omit `linkedInAccountId` to connect a new account. Kenso creates the account with `status`
`connecting` and returns its id. Send `linkedInAccountId` (or `linkedinAccountId`) to reconnect
that account, for example when its `status` is `credentials_error` or `disconnected`.
`importConnections: true` on a new account imports its LinkedIn connections into Accounts once it
connects. It needs the `linkedin_connections_import` feature and is ignored without it. A reconnect ignores
`importConnections` and keeps the account's setting.
`networkOnly: true` connects a network-only account: Kenso syncs its connections and chats but never adds it
to a campaign or sends from it on its own. It needs the `warm_paths_v2` feature. A reconnect ignores
`networkOnly` and keeps the account's setting.
A Network member's account is always network-only: Kenso connects it network-only whatever `networkOnly`
says, and a reconnect makes an account they connected network-only. It still takes a LinkedIn seat on your plan.

Any member may call it, Network members included. A member with Delivery edit can connect a new account and
reconnect any account. A member with only the `approve_own_sends` permission, a Network member among them,
can connect one account of their own and reconnect only that one.

Errors:

- `400 validation_failed`: LinkedIn outreach is not on for this workspace, or detail code
`feature_off` on `networkOnly` when the workspace does not have the `warm_paths_v2` feature.
- `402 plan_limit_reached`: the plan has no LinkedIn seat left, or the workspace's credits do not cover the
account's first month.
- `402 trial_cap_reached`: the workspace is on the Growth trial and already holds its one LinkedIn or
WhatsApp account. `error.refusal` names the cap (`linkedin_accounts`) and offers Upgrade.
- `403 permission_denied`: the caller has neither Delivery edit nor `approve_own_sends`.
- `403 forbidden`, detail code `not_your_linkedin`: a member with only `approve_own_sends` asked
to reconnect another member's account.
- `403 forbidden`: the caller is a workspace key. A LinkedIn seat is a person's own, and a workspace key is
not a person.
- `404 not_found`: `linkedInAccountId` is not an account in this workspace.
- `409 conflict`, detail code `reconnect_instead`: a member with only `approve_own_sends` already
has an account here. The message names the id to reconnect.
- `503 service_unavailable`: LinkedIn is rate limited. Try again shortly.

Open to any workspace member.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/linkedin-accounts/POST/v1/linkedin-accounts/connect-sessions)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `linkedInAccountId` | integer (int64) | no | The LinkedIn account to reconnect. Omit it to connect a new account. `linkedinAccountId` is accepted too, and both must match when you send both. |
| `importConnections` | boolean | no | Set to `true` to import the new account's LinkedIn connections into Accounts once it connects. It needs the `linkedin_connections_import` feature and is ignored without it. A reconnect ignores it and keeps the account's setting. |
| `networkOnly` | boolean | no | Set to `true` to connect a network-only account: Kenso syncs its LinkedIn connections and chats so the workspace can find warm paths through them, but never adds it to a campaign or sends from it on its own. It needs the `warm_paths_v2` feature: without it `true` is refused. A reconnect ignores it and keeps the account's setting. A Network member's account is network-only whatever this says. |

### Response 201

`data` is a `LinkedInConnectSession`.

| Field | Type | Description |
| --- | --- | --- |
| `linkedInAccountId` | integer (int64) | The LinkedIn account the session connects: a new account with status `connecting`, or the account being reconnected. |
| `url` | string | The hosted page where the user signs in to LinkedIn. Open it within one hour. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/linkedin-accounts/connect-sessions" \
  -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 '{
  "linkedInAccountId": 812,
  "importConnections": true,
  "networkOnly": true
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "linkedInAccountId": 812,
    "url": "https://example.com"
  }
}
```
