> 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 can launch

> **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 can launch

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

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

Returns whether the campaign can launch, each condition that stands in the way, and an estimate of how long
sending will take. Read it before `POST /v1/campaigns/{campaignId}/launch`.

`reasons` lists what blocks the launch, plus advisory notices that do not. `warnings` never change
`canLaunch`. `approval_required` means your client was asked and the launch is refused until they
approve; `approval_will_be_requested` means nobody was asked yet, and the launch will ask them and then wait.
Both list what waits in `kinds`. On a campaign that translates its steps, a
`localization_incomplete` warning per language names the steps with no approved translation and whether
those contacts get the source text or are held. When the estimate cannot be calculated, its counts are omitted and
a `sending_estimate_unavailable` warning says why.

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/launch-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 `LaunchReadiness`.

| Field | Type | Description |
| --- | --- | --- |
| `canLaunch` | boolean | True when nothing in `reasons` blocks the launch. Some reasons are advisory and leave it true. |
| `reasons` | array of LaunchReadinessReason | Conditions that stop the launch, plus advisory notices. Empty when there is nothing to report. |
| `warnings` | array of LaunchReadinessReason | Conditions that do not stop the launch but change how the campaign sends. They never change `canLaunch`. |
| `contactLimit` | integer (int32) | The campaign's contact limit used for the estimate. This and the other estimate counts are omitted when the estimate cannot be calculated; the `sending_estimate_unavailable` warning then says why. |
| `contactLimitPeriod` | string | What `contactLimit` and the counts below cover: `month` for one month, else `total`. Omitted with the estimate. |
| `emailStepCount` | integer (int32) | Number of email steps in the sequence. Omitted with the estimate. |
| `totalEmailCount` | integer (int32) | Emails the campaign sends in total: the contact limit times the email steps before it sends, or the emails sent plus those left once it sends. Omitted with the estimate. |
| `dailySendingLimit` | integer (int32) | Emails per day the campaign's inboxes can send for it. Omitted with the estimate. |
| `estimatedDayCount` | integer (int32) | Days until every email is sent at that daily rate. Omitted with the estimate. |
| `forecast` | LaunchForecast | Kenso's live sending forecast for the campaign. Omitted when there is none. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/campaigns/812/launch-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": {
    "canLaunch": true,
    "reasons": [],
    "warnings": [
      {
        "code": "sender_domain_without_click_host",
        "message": "1 sending domain(s) on this campaign have no ready click-tracking host of their own: outreach.example.net (Kenso is still setting up link.outreach.example.net).",
        "fixUrl": "delivery?tab=analytics"
      }
    ],
    "contactLimit": 2500,
    "contactLimitPeriod": "total",
    "emailStepCount": 3,
    "totalEmailCount": 7500,
    "dailySendingLimit": 300,
    "estimatedDayCount": 25
  }
}
```

## Types

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

### LaunchReadinessReason

One condition that blocks the launch, an advisory notice, or a warning.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | no | Stable code for the condition, such as `invalid_schedule`, `missing_prompt_coverage`, `approval_required` or `sending_suspended`. New codes may be added. The deliverability warnings are `sender_domain_without_click_host`, `html_step_on_google_track`, `smtp_inbox_daily_limit_above_10` and `smtp_domain_over_20_inboxes`; `GET /v1/deliverability-rules` names the rule behind each. |
| `message` | string | no | Explanation of the condition, ready to show to a person. |
| `fixUrl` | string | no | Relative app link to the page where the condition can be fixed. Omitted when there is none. |
| `kinds` | array of string | no | For `approval_required` and `approval_will_be_requested` only: what the launch waits on your client to approve, such as `copy`, `lead_list`, `settings`, `icp`, `report` or `account_plan`. Omitted for other codes. |
| `refusal` | Refusal | no | For `free_plan_sending_needs_plan`, `workspace_read_only` and `card_required` only: the refusal launch answers `402` with (code `FREE_PLAN_SENDING_NEEDS_PLAN` or `WORKSPACE_READ_ONLY` with remedy `Upgrade`, or `CARD_REQUIRED` with remedy `UpdatePaymentMethod`). Omitted for other codes. |

### LaunchForecast

Kenso's sending forecast for a campaign, refreshed every few minutes.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `status` | string | no | Forecast state: `forecasted`, `ongoing`, `paused`, `not_started`, `completed` or `unavailable`. |
| `progress` | number (double) | no | Share of the planned emails already sent, from 0 to 1. Omitted when unknown. |
| `estimatedFinishAt` | string (date-time) | no | When the last planned email should go out (UTC). Omitted when it cannot be estimated. |
| `confidence` | string | no | How reliable the forecast is: `none`, `low`, `medium` or `high`. |
| `reasonCodes` | array of string | no | What limits the forecast, such as `zero_eligible_capacity`, `snapshot_expired`, `simulation_horizon_exceeded` or `invalid_sending_window`. Empty when nothing does. |
| `statusExplanation` | string | no | Why there is no forecast, ready to show to a person. Returned only when `status` is `unavailable`. |
| `remainingEmailCount` | integer (int32) | no | Emails still to send. Omitted when unknown. |
| `effectiveDailyCapacity` | integer (int32) | no | Emails per day the campaign gets from its inboxes' shared capacity. Omitted when unknown. |
| `scheduledNext3DayCount` | integer (int32) | no | Emails already queued or planned for the next 3 UTC days. Kenso plans about 36 hours ahead, so this usually covers about one sending day. Use `projectedNext3DayCount` for three-day volume. |
| `effectiveScheduledNext3DayCount` | integer (int32) | no | Equal to `scheduledNext3DayCount` while the campaign is sending, and 0 while it is paused (the queued emails stay in `scheduledNext3DayCount`). Add this field, not the queued one, when you total capacity across campaigns. |
| `projectedNext3DayCount` | integer (int32) | no | Expected emails over the next 3 days: what is queued for today plus the daily capacity of the next two sending days, capped by the emails left to send. |
| `effectiveProjectedNext3DayCount` | integer (int32) | no | Equal to `projectedNext3DayCount` while the campaign is sending, else 0. |
| `readyContactCount` | integer (int32) | no | Contacts ready to send to. Omitted when unknown. |
| `assignedTodayCount` | integer (int32) | no | Emails queued for today's send day, in the campaign's time zone. Omitted when unknown. |
| `acceptedTodayCount` | integer (int32) | no | Emails accepted for sending today, in the campaign's time zone. Omitted when unknown. |
| `calculatedAt` | string (date-time) | no | When the forecast was calculated (UTC). |
| `isStale` | boolean | no | True when the forecast is more than 15 minutes old. |

### Refusal

Why a plan rule or usage limit refused the request, and how to lift it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | no | Stable refusal code in upper case, such as `CAMPAIGN_LIMIT_REACHED` or `INSUFFICIENT_CREDITS`. |
| `metric` | string | no | What the limit counts: `Campaigns`, `Leads`, `Emails`, `LinkedInSeats` or `AiCredits`, `jobs_export_rows` or `funding_export_rows` for an export allowance, `credit_pack_credits`, `credit_spend_usd_7d`, `domains` or `mailboxes` for a limit on a new paying workspace, or for a Kenso Lifetime cap its key: `workspaces`, `inboxes`, `contacts`, `email_verifications_day`, `email_verifications_month`, `people_results_day`, `company_results_day`, `funding_results_day`, `job_post_results_day`, `website_visits_month` or `visitor_lookups_day`. Omitted when a plan rule, not a count, refused the request. |
| `used` | integer (int32) | no | How much of the limit is used, in the unit of `metric`. Omitted when the refusal has no count. |
| `limit` | integer (int32) | no | The limit, in the unit of `metric`. Omitted when the refusal has no count. |
| `remaining` | integer (int32) | no | How much of the limit is left, in the unit of `metric`. Omitted when the refusal has no count. |
| `planType` | string | no | The workspace's plan as its snake plan id, for example `free`, `legacy_core` or `growth`. |
| `remedy` | string | no | What lifts the refusal: `Upgrade`, `BuyAddOn`, `UpdatePaymentMethod` or `ContactSupport`. `None` means no action of yours lifts it. |
| `unlocksAt` | string (date-time) | no | When the limit lifts by itself, in UTC: for a limit on a new paying workspace once it has paid an invoice, and for a Kenso Lifetime daily or monthly cap its reset (00:00 UTC, or the 1st of the month). Omitted on every other refusal. |
| `requiredMillicredits` | integer (int64) | no | On a credit refusal, the millicredits the action needed. 1,000 millicredits are one credit. Omitted on every other refusal. |
| `availableMillicredits` | integer (int64) | no | On a credit refusal, the millicredits available. On `FREE_CREDITS_NOT_ELIGIBLE`, only the credits that may pay for inboxes and domains. Omitted on every other refusal. |
| `restrictedMillicredits` | integer (int64) | no | On `FREE_CREDITS_NOT_ELIGIBLE`, the free and bonus millicredits in the balance that cannot pay for inboxes and domains. Omitted on every other refusal. |
| `feature` | string | no | On `PLAN_FEATURE_NOT_AVAILABLE`, the plan feature the plan does not include, in snake case (for example `website_visitor_id`). Omitted on every other refusal. |
| `requiredPlan` | string | no | On `PLAN_FEATURE_NOT_AVAILABLE`, the cheapest plan that includes `feature`, in snake case (for example `growth`). For a feature the self-serve trial locks (`browser_runs`), the trial's own plan, which paying for unlocks it. Omitted on every other refusal. |
| `requiredTier` | integer (int32) | no | On a Kenso Lifetime refusal, the lowest tier that lifts it: the next tier with a higher cap, or the lowest tier that includes `feature`. Omitted at the top tier, when no tier includes the feature, and on every other refusal. |
| `upgradeUrl` | string | no | On a Kenso Lifetime refusal that a higher tier lifts, the AppSumo page where the buyer upgrades their license. Omitted until Kenso has read that page from AppSumo, when no tier lifts the refusal, and on every other refusal. |
