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

# Segment email sequences: Restore a segment's email sequence version

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

## Restore a segment's email sequence version

`POST /v1/segments/{segmentId}/email-sequence/versions/{versionId}/restore` - operationId `segment-email-sequences.restore-version`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 4,800 requests a minute per API key |

Writes the steps of a saved version into the segment's live email sequence and adds a new version that records
the restore. `newVersionNumber` in the response is that version's number.

Kenso checks the version's steps with today's sequence rules and URL reputation check before it writes them.

Errors:

- `400 validation_failed`: the version has no steps while the live sequence has some, or a step breaks today's sequence rules.
- `400 validation_failed` with `link_reputation_blocked` details: a link failed the URL reputation check. Each detail's `field` is `steps.subject` or `steps.body`, and `stepId` is the live step the restore would overwrite.
- `404 not_found`: the segment does not exist in this workspace, it has no email sequence of its own, or the version is not one of that sequence's versions.
- `409 conflict`: another version save for this sequence is running. Retry shortly.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/sequences/POST/v1/segments/%7BsegmentId%7D/email-sequence/versions/%7BversionId%7D/restore)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `segmentId` | path | integer (int64) | yes | The segment's id. |
| `versionId` | path | integer (int64) | yes | The id of the version to restore. |
| `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 `SequenceRestore`.

| Field | Type | Description |
| --- | --- | --- |
| `newVersionNumber` | integer (int32) | The number of the new version that records the restore. Omitted when Kenso restored the steps but could not record the version. |
| `versionWarning` | string | Why Kenso could not record the version after it restored the steps. Omitted when it did. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/segments/812/email-sequence/versions/812/restore" \
  -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": {
    "newVersionNumber": 7
  }
}
```
