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

# Email sequences: Get a campaign's email sequence

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

## Get a campaign's email sequence

`GET /v1/campaigns/{campaignId}/email-sequence` - operationId `email-sequences.get`

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

Returns the campaign's own email sequence with its steps. Contacts in a segment that has no email sequence of
its own get this one.

Errors:

- `404 not_found`: the campaign does not exist in this workspace, or it has no email sequence.

Requires Campaigns view.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `campaignId` | path | integer (int64) | yes | The campaign's id. |
| `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 `EmailSequence`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The email sequence's id. |
| `campaignId` | integer (int64) | The id of the campaign the sequence belongs to. |
| `segmentId` | integer (int64) | The id of the segment that owns the sequence. Null for the campaign's own sequence. |
| `name` | string | The sequence's name. |
| `isActive` | boolean | Whether the sequence is on. |
| `steps` | array of EmailSequenceStep | Every step and variant of the sequence, in step order. |
| `createdAt` | string (date-time) | When the sequence was created, in UTC (ISO 8601). |
| `modifiedAt` | string (date-time) | When the sequence last changed, in UTC (ISO 8601). Send it as `expectedModifiedAt` on your next replace so you do not overwrite someone else's change. |
| `contentWarnings` | array of EmailSequenceContentWarning | What Kenso's content checks found in the steps you saved, such as a link whose text names another site. Only a replace response with findings carries it. Omitted otherwise. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/campaigns/812/email-sequence" \
  -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": {
    "id": 2210,
    "campaignId": 4821,
    "segmentId": 1207,
    "name": "Engineering leaders",
    "isActive": true,
    "steps": [
      {
        "id": 8841,
        "stepOrder": 1,
        "variant": "a",
        "subject": "Onboarding new engineers at {company}",
        "body": "Hi {firstName},\n\nMost engineering teams lose a new hire's first two weeks to setup and access requests. We help teams like yours get that down to two days.\n\nWorth a 15-minute look next week?\n\n{sender_first_name}",
        "bodyFormat": "plain",
        "waitDays": 0,
        "isActive": true,
        "openTrackingEnabled": false,
        "handwrittenEnabled": false
      },
      {
        "id": 8842,
        "stepOrder": 2,
        "variant": "a",
        "subject": "",
        "body": "Hi {firstName}, following up on this. Happy to send a 2-minute video instead if that is easier.\n\n{sender_first_name}",
        "bodyFormat": "plain",
        "waitDays": 3,
        "isActive": true,
        "openTrackingEnabled": false,
        "handwrittenEnabled": false
      }
    ],
    "createdAt": "2026-09-23T15:02:11Z",
    "modifiedAt": "2026-10-14T09:41:27Z"
  }
}
```

## Types

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

### EmailSequenceStep

One variant of one email step in a sequence.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | integer (int64) | no | The step's id. Send it back in a replace to update this step. |
| `campaignId` | integer (int64) | no | The campaign whose email sequence holds this step. Omitted on sequence reads, which carry it on the sequence. |
| `stepOrder` | integer (int32) | no | The step's position in the sequence, starting at 1. The variants of one step share it. |
| `variant` | string | no | The variant of the step for A/B testing: `a`, `b`, `c` or `d`. |
| `name` | string | no | A label for the step. Null when none is set. |
| `subject` | string | no | The subject line, with variables such as `{firstName}` not yet filled in. An empty subject on step 2 or later sends the email as a reply in the thread of the previous email. |
| `body` | string | no | The email body, with variables not yet filled in. `bodyFormat` says how to read it. |
| `bodyFormat` | string | no | How `body` is written: `plain`, `markdown` or `html`. |
| `waitDays` | integer (int32) | no | Days Kenso waits after the previous step is sent before it sends this step. Step 1 ignores it and is usually 0. |
| `isActive` | boolean | no | Whether Kenso sends this variant. An inactive variant is kept but not sent. |
| `openTrackingEnabled` | boolean | no | Stored and returned for compatibility; it does not affect sending. The campaign's `trackOpens` decides whether a send carries the open pixel. |
| `handwrittenEnabled` | boolean | no | Whether Kenso sends the letter part of the body as an image of a handwritten letter. The letter part is the body above the sender signature or the unsubscribe link. |
| `handwrittenBackground` | string | no | The paper behind the handwritten letter: `walnut`, `linen`, `kraft`, `marble`, `deckle` or `notepad`. Null means `walnut`. |
| `handwrittenIntro` | string | no | The line of normal text above the handwritten letter. Null means Kenso's default line, which names the contact and the sender. |
| `warnings` | array of string | no | Advice about this step that never stops a save. An `html` step can carry `html_on_mailbox_inbox` (the campaign sends from a Google or Microsoft mailbox), `html_size_near_cap` (the body is over 80% of the size limit) and `html_external_image:<host>` (an image loads from another site). A replace response can add `html_removed:<what>` for markup Kenso removed, and `studio_pin_removed` on any step whose Studio email the replace unpinned. Null when there is nothing to report. |
| `studioTemplateVersionId` | integer (int64) | no | The Studio email version this step sends, filled in for each contact. Null when the step does not send a Studio email. |
| `studioPin` | StudioPin | no | The state of the Studio email this step sends. Null when the step does not send one. |

### EmailSequenceContentWarning

One finding of Kenso's content checks on a saved email step.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `stepOrder` | integer (int32) | no | The `stepOrder` of the step the finding is about. |
| `variant` | string | no | The variant of the step the finding is about: `a`, `b`, `c` or `d`. |
| `code` | string | no | The rule that found it, as a stable snake_case code such as `link_host_mismatch` (a link's text is a web address that differs from where the link goes). |
| `severity` | string | no | How serious the finding is: `warning`, `hard_warning` or `block`, from least to most serious. |
| `path` | string | no | The part of the step the finding is about, such as `subject` or `body.links`. |
| `message` | string | no | A sentence that explains the finding. |
| `policyVersion` | string | no | The version of the content rules that produced the finding. |

### StudioPin

The Studio email version a step sends, and whether it can still be sent.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `versionId` | integer (int64) | no | The id of the Studio email version. |
| `templateId` | integer (int64) | no | The id of the Studio email the version belongs to. Null when that email no longer exists. |
| `state` | string | no | `ok`, or `stale` when the version is no longer published, is not an email, or its Studio email was deleted. A `stale` step sends the subject and body stored on the step instead. |
