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

# WhatsApp accounts: Start a hosted WhatsApp connect or reconnect 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 [WhatsApp accounts](/docs/api/whatsapp-accounts.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Start a hosted WhatsApp connect or reconnect session

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

| Permission | Credits | Rate limit |
| --- | --- | --- |
| Any workspace member except a Network member | Spends credits, price not on the rate card yet (`whatsapp_account_monthly`) | 10 requests a minute per API key |

Omit `whatsappAccountId` to connect a new account (it shows as `connecting` until the scan completes);
pass it to reconnect. A new account needs one month of credits up front (`400 validation_failed` with the
credit refusal otherwise). On the Growth trial a new account is refused with `402 trial_cap_reached` once the
workspace holds its one LinkedIn or WhatsApp account. A client seat reconnects only the account it connected (`403 forbidden` with
`not_your_whatsapp`). `503 service_unavailable` while WhatsApp is switched off or Unipile is throttled.
A workspace key gets `403 forbidden`: a WhatsApp seat is a person's own, and a workspace key is not a person.

Needs the `whatsapp` 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/whatsapp-accounts/POST/v1/whatsapp-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 |
| --- | --- | --- | --- |
| `whatsappAccountId` | integer (int64) | no |  |

### Response 201

`data` is a `WhatsAppConnectSession`.

| Field | Type | Description |
| --- | --- | --- |
| `whatsappAccountId` | integer (int64) |  |
| `url` | string |  |

### Request

```bash
curl -X POST "https://api.ken.so/v1/whatsapp-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 '{
  "whatsappAccountId": 812
}'
```

### Example response

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