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

# CRM imports

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

Import records from your CRM now.

Integrations. 1 endpoint under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/crm-imports/openapi.json](/docs/api/crm-imports/openapi.json).

- `POST /v1/crm-connections/{connectionId}/imports` - Start a CRM import (`crm-imports.create`): [/docs/api/crm-imports/create.md](/docs/api/crm-imports/create.md)

## Start a CRM import

`POST /v1/crm-connections/{connectionId}/imports` - operationId `crm-imports.create`

| Permission | Rate limit |
| --- | --- |
| Accounts view and the `integrations` permission | 4,800 requests a minute per API key |

Reads every record from the CRM again, in the background. An import writes nothing to the CRM.

The call answers 202 with `startedAt`. Poll `GET /v1/crm-connections/{connectionId}/sync` until
`importRunning` is false.

Errors:

- `402 plan_required`: the workspace is not on a paid plan, or the connection is paused for the plan.
- `404 not_found`: the workspace has no connection with this id.
- `409 import_running`: an import is already running.
- `409 needs_reconnect`: the CRM refused Kenso's access. Reconnect the CRM first.
- `409 invalid_state`: the connection is disconnected.

Requires Accounts view and the `integrations` permission.

Needs the `ingestion` 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/crm-sync/POST/v1/crm-connections/%7BconnectionId%7D/imports)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `connectionId` | path | integer (int64) | yes | The CRM connection's id. |
| `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 202

`data` is a `CrmImport`.

| Field | Type | Description |
| --- | --- | --- |
| `startedAt` | string (date-time) | When the import started, in UTC. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/crm-connections/812/imports" \
  -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": {
    "startedAt": "2026-09-23T15:02:11Z"
  }
}
```

All resources: [/docs.md](/docs.md).
