> 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: Restore deleted 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).

## Restore deleted contacts

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

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 480 requests a minute per API key |

Brings back up to 1,000 deleted contacts, the undo of a delete. Each contact returns to the campaign and
segment it was deleted from, with its emails and fields unchanged. Nothing is charged and no
enrichment runs again.

A restored contact in an active campaign can get its next email steps again. LinkedIn steps that stopped while
the contact was deleted stay stopped. A contact your client removed during a lead list approval comes
back too, and the approval does not change.

`succeeded` lists the ids this call restored, and `restored` counts them. Every other id is in
`failed` with one of these codes:

- `not_deleted`: the contact is not deleted, so nothing changed. `skipped` counts these, and a retry
of an id already restored returns this code.
- `not_found`: the id is not a contact in the workspace.
- `internal_error`: the restore failed. Retry that id.

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.

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

### 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 `ContactBulkRestoreResult`.

| Field | Type | Description |
| --- | --- | --- |
| `restored` | integer (int32) | How many contacts this call restored: the length of `succeeded`. |
| `skipped` | integer (int32) | How many ids were not deleted, so nothing changed: the `not_deleted` entries of `failed`. |
| `succeeded` | array of integer (int64) | Ids of the contacts this call restored. |
| `failed` | array of ContactBulkFailure | One entry for each id the call did not restore, with the reason. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/contacts/bulk-restore" \
  -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": {
    "restored": 2,
    "skipped": 1,
    "succeeded": [
      90125,
      90126
    ],
    "failed": [
      {
        "id": 90131,
        "error": {
          "code": "not_deleted",
          "message": "The contact is not deleted, so nothing changed."
        }
      }
    ]
  }
}
```

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

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