> 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-sync-issues/openapi.json](/docs/api/crm-sync-issues/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# CRM sync issues

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

Records the CRM sync could not write: list, retry or dismiss them.

Integrations. 3 endpoints 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-sync-issues/openapi.json](/docs/api/crm-sync-issues/openapi.json).

- `GET /v1/crm-connections/{connectionId}/sync-issues` - List sync issues (`crm-sync-issues.list`): [/docs/api/crm-sync-issues/list.md](/docs/api/crm-sync-issues/list.md)
- `DELETE /v1/crm-connections/{connectionId}/sync-issues/{issueId}` - Dismiss a sync issue (`crm-sync-issues.dismiss`): [/docs/api/crm-sync-issues/dismiss.md](/docs/api/crm-sync-issues/dismiss.md)
- `POST /v1/crm-connections/{connectionId}/sync-issues/{issueId}/retry` - Retry a sync issue (`crm-sync-issues.retry`): [/docs/api/crm-sync-issues/retry.md](/docs/api/crm-sync-issues/retry.md)

## List sync issues

`GET /v1/crm-connections/{connectionId}/sync-issues` - operationId `crm-sync-issues.list`

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

Lists the writes the CRM refused, newest first. The Kenso app shows them under Needs attention. Retry or dismiss
each one. It also answers for a disconnected connection.

Errors:

- `400 validation_failed`: `limit` or `cursor` is not valid.
- `404 not_found`: the workspace has no connection with this id.

Requires Accounts view.

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/GET/v1/crm-connections/%7BconnectionId%7D/sync-issues)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `connectionId` | path | integer (int64) | yes | The CRM connection's id. |
| `limit` | query | integer (int32) | no | Page size, from 1 to 200. Default 50. |
| `cursor` | query | string | no | The `pagination.nextCursor` of the previous page. Omit it for the first page. |
| `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 list of `CrmSyncIssue`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The issue's id. |
| `kind` | string | What Kenso tried to write: `record`, `activity`, `opt_out`, `deal`, `task`, `list` or `ensure_fields` (creating Kenso's own CRM fields). |
| `entityRef` | string | The Kenso record the write was for, such as `person:88231`. |
| `error` | string | The CRM's error message. Omitted when the CRM gave none. |
| `attempts` | integer (int32) | How many times Kenso tried the write. |
| `createdAt` | string (date-time) | When the write was first queued, in UTC. |
| `updatedAt` | string (date-time) | When the issue last changed, in UTC. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/crm-connections/812/sync-issues?limit=50" \
  -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": [
    {
      "id": 812,
      "kind": "record",
      "entityRef": "person:88231",
      "error": "string",
      "attempts": 1,
      "createdAt": "2026-09-23T15:02:11Z",
      "updatedAt": "2026-09-23T15:02:11Z"
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

## Dismiss a sync issue

`DELETE /v1/crm-connections/{connectionId}/sync-issues/{issueId}` - operationId `crm-sync-issues.dismiss`

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

Removes a refused write from the list. Kenso never sends that write to the CRM. It also works on a disconnected
connection.

Errors:

- `404 not_found`: the connection does not exist, or no issue with this id needs attention on it.

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/DELETE/v1/crm-connections/%7BconnectionId%7D/sync-issues/%7BissueId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `connectionId` | path | integer (int64) | yes | The CRM connection's id. |
| `issueId` | path | integer (int64) | yes | The sync issue's id, from `GET /v1/crm-connections/{connectionId}/sync-issues`. |
| `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 204

### Request

```bash
curl -X DELETE "https://api.ken.so/v1/crm-connections/812/sync-issues/812" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```http
HTTP/1.1 204 No Content
```

## Retry a sync issue

`POST /v1/crm-connections/{connectionId}/sync-issues/{issueId}/retry` - operationId `crm-sync-issues.retry`

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

Puts a refused write back in the queue. Kenso sends it to the CRM again on its next pass, and the issue leaves the
list.

Errors:

- `404 not_found`: the connection does not exist, or no issue with this id needs attention on it.
- `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/sync-issues/%7BissueId%7D/retry)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `connectionId` | path | integer (int64) | yes | The CRM connection's id. |
| `issueId` | path | integer (int64) | yes | The sync issue's id, from `GET /v1/crm-connections/{connectionId}/sync-issues`. |
| `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 204

### Request

```bash
curl -X POST "https://api.ken.so/v1/crm-connections/812/sync-issues/812/retry" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```http
HTTP/1.1 204 No Content
```

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