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

# Campaigns: Retry failed enrichment

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

## Retry failed enrichment

`POST /v1/campaigns/{campaignId}/retry-enrichment` - operationId `campaigns.retry-enrichment`

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

Clears the campaign's failed website reads and failed email searches so Kenso tries those contacts and
companies again, and returns how many were cleared. It does not restart processing and does not change
qualification, personalization or what was sent. If enrichment is paused, the failures are still cleared and
the retries wait until it resumes. Calling it when nothing failed returns zero counts.

Errors:

- `400 validation_failed`: the campaign is archived.
- `404 not_found`: the campaign does not exist in this workspace.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/campaigns/POST/v1/campaigns/%7BcampaignId%7D/retry-enrichment)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `campaignId` | path | integer (int64) | yes | Id of the campaign. |
| `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 `RetryEnrichment`.

| Field | Type | Description |
| --- | --- | --- |
| `companyStatusesCleared` | integer (int32) | Companies whose website could not be read or had no usable content. |
| `scrapeFailuresCleared` | integer (int32) | Website reads that failed. |
| `contactStatusesCleared` | integer (int32) | Contacts whose email search failed. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/campaigns/812/retry-enrichment" \
  -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": {
    "companyStatusesCleared": 14,
    "scrapeFailuresCleared": 9,
    "contactStatusesCleared": 31
  }
}
```
