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

# Contacts: Resume sequences for paused contacts

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

## Resume sequences for paused contacts

`POST /v1/contacts/bulk-resume` - operationId `contacts.bulk-resume`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit and the `launch` permission | 480 requests a minute per API key |

Restarts the campaign sequence of up to 1,000 paused contacts. Only a stop with `sequenceStopReason`
`paused` is cleared. Kenso plans the next steps of resumed contacts on its next planning pass,
about every 10 minutes, and a held LinkedIn step picks up within the hour.

`succeeded` lists the ids this call resumed. Every other id is in `failed` with one of these codes:

- `not_paused`: the sequence is running, or it stopped for another reason, which stays.
- `not_found`: the id is not a contact in the workspace.

Errors:

- `400 validation_failed`: `ids` is missing or empty, holds more than 1,000 ids, or holds an id that
is not positive.

Requires Campaigns edit and the `launch` permission.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/contacts/POST/v1/contacts/bulk-resume)

### 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 |
| --- | --- | --- | --- |
| `ids` | array of integer (int64) | yes | Required. From 1 to 1,000 contact ids in the workspace. |

### Response 200

`data` is a `ContactBulkResult`.

| Field | Type | Description |
| --- | --- | --- |
| `succeeded` | array of integer (int64) | Ids of the contacts the call changed or saved. |
| `failed` | array of ContactBulkFailure | One entry for each contact or row the call did not change, with the reason. |
| `results` | array of ContactCreateRowResult | One item per input row of `POST /v1/campaigns/{campaignId}/contacts`, in request order. Only that call returns it. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/contacts/bulk-resume" \
  -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 '{
  "ids": [
    90125,
    90126,
    90131
  ]
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "succeeded": [
      90125,
      90126
    ],
    "failed": [
      {
        "id": 90131,
        "error": {
          "code": "not_found",
          "message": "No contact with this id in the workspace."
        }
      }
    ]
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### ContactBulkFailure

One contact or row a bulk call did not change, and why.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | integer (int64) | no | The contact id. Omitted for a row Kenso refused before saving it. |
| `index` | integer (int32) | no | The row's position in the request, from 0. Only on `POST /v1/campaigns/{campaignId}/contacts`. |
| `error` | ContactBulkError | no | Why the contact or row failed. |

### ContactCreateRowResult

What Kenso did with one row of `POST /v1/campaigns/{campaignId}/contacts`.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `index` | integer (int32) | no | The row's position in `contacts`, from 0. |
| `status` | string | no | What Kenso did with the row: `created` (a new contact), `updated` (the campaign already had the contact), `skipped` or `failed`. |
| `id` | integer (int64) | no | The contact id, when Kenso saved the row. |
| `reason` | string | no | Why a row was skipped or failed: `duplicate` (an earlier row or an existing contact), `blocklisted` (on the workspace blocklist), `already_contacted` (in another campaign, or emailed inside the campaign's recently-emailed window), `limit_reached` (the plan's contact allowance is used up), `invalid_email`, `excluded` (a campaign exclusion rule such as an excluded country), `validation` (another field rule) or `other`. On Kenso Lifetime, `limit_reached` also means the license's contacts (one pool across its workspaces) are used up. |
| `message` | string | no | For a skipped or failed row, a readable explanation. |
| `sendable` | boolean | no | On a saved row, false when the contact will not get campaign steps: it is do-not-contact, or Kenso added it unqualified, for example because no contact allowance was left. |

### ContactBulkError

The error for one contact or row of a bulk call.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | no | A stable error code, such as `not_found`, `validation_failed`, `not_deleted`, `not_paused`, `already_stopped`, `do_not_contact`, `video_in_use` or `internal_error`. Each operation lists the codes it returns. |
| `message` | string | no | A readable explanation. |
