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

# Segments: Give a provider track its own sequence, or share the segment's

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

## Give a provider track its own sequence, or share the segment's

`PUT /v1/segments/{segmentId}/provider-tracks/{track}` - operationId `segments.set-provider-track`

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

Sets the sequence one provider track of a segment sends. The track is `google`, `microsoft` or
`other` (everyone else). Format follows the recipient's mail provider: a recipient on Google gets plain
text, a recipient on Microsoft gets the email as written.

Send `{ "sequence": "own" }` to give the track its own copy of the segment's email sequence: read and
replace that copy with `/v1/segments/{segmentId}/email-sequence` on the track's `sequenceSegmentId`.
Editing one track's copy never changes another's. The segment needs an email sequence of its own first: a
segment that sends the campaign's emails answers `no_sequence`, so save those emails onto the segment with
`PUT /v1/segments/{segmentId}/email-sequence` before you ask for a copy. Send
`{ "sequence": "shared" }` to drop the track's copy: its contacts continue on the segment's sequence at the
same step. Both are safe to repeat. Returns the tracks as `GET /v1/segments/{segmentId}/provider-tracks`
does.

Errors:

- `400 validation_failed`: detail code `feature_disabled` (the workspace does not have provider
tracks), `invalid_track`, `invalid_sequence`, `no_sequence` (the segment has no email
sequence to copy) or `sequence_has_conditions` (a sequence with conditions has one copy for all tracks).
- `404 not_found`: the segment does not exist in this workspace.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/segments/PUT/v1/segments/%7BsegmentId%7D/provider-tracks/%7Btrack%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `segmentId` | path | integer (int64) | yes | Id of the segment. |
| `track` | path | string | yes | The provider track: `google`, `microsoft` or `other`. |
| `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`. |

### Request body

`application/json`, optional.

The sequence the track sends: `own` or `shared`.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `sequence` | string | no | `own` gives the track its own copy of the segment's sequence; `shared` drops that copy. |

### Response 200

`data` is a `ProviderTracks`.

| Field | Type | Description |
| --- | --- | --- |
| `campaignId` | integer (int64) | Id of the segment's campaign. |
| `segmentId` | integer (int64) | Id of the segment. |
| `enabled` | boolean | True when the campaign is on provider tracks. False means its sends go out as before. |
| `googleFollowUpsAsWritten` | boolean | True when the Google track sends the steps after the first as written. The first step stays plain text. |
| `isPartial` | boolean | True when the segment has more than 100,000 contacts: the counts then cover the first 100,000 by id. |
| `tracks` | array of ProviderTrack | The three tracks, in the order `google`, `microsoft`, `other`. |

### Request

```bash
curl -X PUT "https://api.ken.so/v1/segments/812/provider-tracks/google" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "sequence": "own"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "campaignId": 4821,
    "segmentId": 1207,
    "enabled": true,
    "googleFollowUpsAsWritten": false,
    "isPartial": false,
    "tracks": [
      {
        "track": "google",
        "leadCount": 312,
        "sequenceSegmentId": 1219,
        "hasOwnSequence": true,
        "sameAs": [],
        "sendsPlainText": true
      },
      {
        "track": "microsoft",
        "leadCount": 241,
        "sequenceSegmentId": 1207,
        "hasOwnSequence": false,
        "sameAs": [
          "other"
        ],
        "sendsPlainText": false
      },
      {
        "track": "other",
        "leadCount": 87,
        "sequenceSegmentId": 1207,
        "hasOwnSequence": false,
        "sameAs": [
          "microsoft"
        ],
        "sendsPlainText": false
      }
    ]
  }
}
```

## Types

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

### ProviderTrack

One provider track of a segment.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `track` | string | no | The track: `google`, `microsoft` or `other`. |
| `leadCount` | integer (int32) | no | The segment's contacts on this track that can still get an email. A contact whose provider is not known yet counts under `google`. |
| `sequenceSegmentId` | integer (int64) | no | Id of the segment whose `/v1/segments/{segmentId}/email-sequence` holds this track's copy: the track's own when `hasOwnSequence` is true, else this segment. |
| `hasOwnSequence` | boolean | no | True when the track has its own sequence. False while it shares the segment's sequence. |
| `sameAs` | array of string | no | The other tracks that share this track's copy. Empty when the track has its own sequence. |
| `sendsPlainText` | boolean | no | True when the track sends as plain text: `google`. |
