> 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: Check whether a campaign's workflows can start

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

## Check whether a campaign's workflows can start

`GET /v1/campaigns/{campaignId}/workflow-readiness` - operationId `campaigns.get-workflow-readiness`

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

Runs the checks that must pass before the campaign's enrichment, email verification and AI workflows can start,
and returns each one with `isPassed`. The checks cover imported contacts or an active signal, the contact
limit, the name, the schedule, the email sequence and its AI variables. Whether the campaign can start sending
is `GET /v1/campaigns/{campaignId}/launch-readiness`.

Errors:

- `404 not_found`: the campaign does not exist in this workspace.

Requires Campaigns view.

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

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

| Field | Type | Description |
| --- | --- | --- |
| `canStart` | boolean | True when every check passed. |
| `checks` | array of WorkflowReadinessCheck | Every check that applies to the campaign, passed or not. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/campaigns/812/workflow-readiness" \
  -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": {
    "canStart": false,
    "checks": [
      {
        "code": "contacts_imported",
        "message": "Campaign must have imported contacts before processing can start.",
        "isPassed": true
      },
      {
        "code": "campaign_name_configured",
        "message": "Campaign name is required before processing can start.",
        "isPassed": true
      },
      {
        "code": "ai_variables_resolved",
        "message": "All AI variables used in email copy must map to prompts that produce output at runtime before processing can start.",
        "isPassed": false
      }
    ]
  }
}
```

## Types

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

### WorkflowReadinessCheck

One readiness check and its result.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | no | The check: `contacts_imported`, `trigger_definitions_configured`, `email_sequence_configured`, `email_sequence_versions_unique`, `ai_variables_resolved`, `campaign_name_configured`, `contact_limit_configured` or `sending_schedule_configured`. New codes may be added. |
| `message` | string | no | Explanation of the check's result, ready to show to a person. |
| `isPassed` | boolean | no | True when the check passed. |
