Skip to Content
Integrations

CRM sync issues

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

Integrations3 endpointsKen-Version: 2026-11-02AuthenticationWorkspacesErrors
MarkdownOpenAPI

Path parameters

The endpoints whose path names one of these take it as described here. An endpoint's own table lists a path parameter only when it describes it differently.

NameInTypeRequiredDescription
connectionIdpathinteger (int64)requiredThe CRM connection's id.
issueIdpathinteger (int64)requiredThe sync issue's id, from GET /v1/crm-connections/{connectionId}/sync-issues.

Headers

The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.

NameInTypeRequiredDescription
Ken-Versionheaderstring, one of: 2026-11-02, 1.1optionalThe 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy.
X-Ken-Workspace-Idheaderinteger (int64)optionalThe 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.

List sync issues

GET/v1/crm-connections/{connectionId}/sync-issuescrm-sync-issues.list
Permission
Accounts view
Rate limit
12,000 requests a minute per API key
Needs the ingestion feature on your workspace. Until it is on, calls answer 404.

Try it on developer.ken.so

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.

Parameters

NameInTypeRequiredDescription
limitqueryinteger (int32)optionalPage size, from 1 to 200. Default 50.
cursorquerystringoptionalThe pagination.nextCursor of the previous page. Omit it for the first page.
Request
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"

Response 200

data is a list of CrmSyncIssue. Each item has these fields. The response also carries pagination.

Show the 7 response fields and an example

The fields and an example are also on this endpoint's Markdown page.

Dismiss a sync issue

DELETE/v1/crm-connections/{connectionId}/sync-issues/{issueId}crm-sync-issues.dismiss
Permission
Accounts view and the integrations permission
Rate limit
4,800 requests a minute per API key
Needs the ingestion feature on your workspace. Until it is on, calls answer 404.

Try it on developer.ken.so

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.

Request
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"

Response 204

Response 204
HTTP/1.1 204 No Content

Retry a sync issue

POST/v1/crm-connections/{connectionId}/sync-issues/{issueId}/retrycrm-sync-issues.retry
Permission
Accounts view and the integrations permission
Rate limit
4,800 requests a minute per API key
Needs the ingestion feature on your workspace. Until it is on, calls answer 404.

Try it on developer.ken.so

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.

Request
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"

Response 204

Response 204
HTTP/1.1 204 No Content

On this page