Skip to Content
Campaigns

Segment LinkedIn sequences

The LinkedIn sequence of one segment and its saved versions.

Campaigns6 endpointsKen-Version: 2026-11-02AuthenticationWorkspacesErrors
MarkdownOpenAPI

Path parameters

The endpoints whose path names one of these take it as described here. An endpoint's own table lists a path parameter only when it describes it differently.

NameInTypeRequiredDescription
segmentIdpathinteger (int64)requiredThe segment's id.

Headers

The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.

NameInTypeRequiredDescription
Ken-Versionheaderstring, one of: 2026-11-02, 1.1optionalThe 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy.
X-Ken-Workspace-Idheaderinteger (int64)optionalThe 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.

Get a segment's LinkedIn sequence

GET/v1/segments/{segmentId}/linkedin-sequencesegment-linkedin-sequences.get
Permission
Campaigns view
Rate limit
12,000 requests a minute per API key

Try it on developer.ken.so

Returns the segment's own LinkedIn steps. An empty steps list means the segment has none, and its contacts get the campaign's LinkedIn sequence.

Errors:

  • 404 not_found: the segment does not exist in this workspace.

Requires Campaigns view.

Request
curl -X GET "https://api.ken.so/v1/segments/812/linkedin-sequence" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"

Response 200

data is a LinkedInSequence.

Show the 4 response fields and an example

The fields and an example are also on this endpoint's Markdown page.

Replace a segment's LinkedIn sequence

PUT/v1/segments/{segmentId}/linkedin-sequencesegment-linkedin-sequences.replace
Permission
Campaigns edit
Rate limit
4,800 requests a minute per API key

Try it on developer.ken.so

Replaces every step of the segment's own LinkedIn sequence with the steps you send. Once the segment has steps, its contacts get them instead of the campaign's. An empty steps list removes them all, and the segment's contacts go back to the campaign's LinkedIn sequence.

The rules of PUT /v1/campaigns/{campaignId}/linkedin-sequence apply. anchorEmailStepOrder must name a step of the segment's own email sequence when it has steps.

Errors:

  • 400 validation_failed: a step breaks a LinkedIn sequence rule, or uses a variable Kenso does not know.
  • 400 validation_failed: a step needs a feature that is off for the workspace: linkedin_engagement for engagement steps, linkedin_voice_notes for voice_note steps, or linkedin_ai_notes for noteMode ai.
  • 404 not_found: the segment does not exist in this workspace.

Requires Campaigns edit.

Request body

application/json, optional.

FieldTypeRequiredDescription
stepsarray of ReplaceLinkedInSequenceStepRequestrequiredEvery step and variant the sequence should have. Required. A row with an id updates that row, a row without one updates the row with the same stepOrder, variant and stepType or is added, and rows you leave out are deleted. An empty list deletes every LinkedIn step.
instructionstringoptionalThe person's request that led to this change, in their own words when you have them. Optional. Kenso keeps it with the edit history of the steps this save changes, marked as reported by your agent, and keeps the first 2,000 characters. Leave it out when no person asked for the change; never invent one.
Request
curl -X PUT "https://api.ken.so/v1/segments/812/linkedin-sequence" \
  -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 '{
  "steps": [
    {
      "stepOrder": 1,
      "stepType": "connection_request",
      "variant": "a",
      "body": "Hi {firstName}, I work with engineering leaders on onboarding. Glad to connect.",
      "waitDays": 1,
      "anchorEmailStepOrder": 1,
      "positionInGap": 0,
      "conditionType": "none",
      "isOptional": false,
      "openProfileOnly": false,
      "waitFromCondition": false,
      "isActive": true,
      "noteMode": "template",
      "id": 9301
    },
    {
      "stepOrder": 2,
      "stepType": "message",
      "variant": "a",
      "body": "Thanks for connecting, {firstName}. Did my email about onboarding new engineers reach you?",
      "waitDays": 2,
      "anchorEmailStepOrder": 1,
      "positionInGap": 1,
      "conditionType": "accepted",
      "isOptional": false,
      "openProfileOnly": false,
      "waitFromCondition": false,
      "isActive": true,
      "id": 9302
    }
  ],
  "instruction": "Message on LinkedIn once the invitation is accepted."
}'

Response 200

data is a LinkedInSequence.

Show the 4 response fields and an example

The fields and an example are also on this endpoint's Markdown page.

List a segment's LinkedIn sequence versions

GET/v1/segments/{segmentId}/linkedin-sequence/versionssegment-linkedin-sequences.list-versions
Permission
Campaigns view
Rate limit
12,000 requests a minute per API key

Try it on developer.ken.so

Returns the saved versions of the segment's own LinkedIn sequence, newest first. Kenso adds a version when you save one or restore one, and when a segment restore brings the LinkedIn sequence back. Replacing the sequence does not add a version.

Errors:

  • 400 validation_failed: limit is out of range, or cursor is invalid.
  • 404 not_found: the segment does not exist in this workspace.

Requires Campaigns view.

Parameters

NameInTypeRequiredDescription
limitqueryinteger (int32)optionalVersions per page, from 1 to 100. Defaults to 20.
cursorquerystringoptionalThe nextCursor from the previous page. Omit it for the first page.
Request
curl -X GET "https://api.ken.so/v1/segments/812/linkedin-sequence/versions?limit=20" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"

Response 200

data is a list of SequenceVersion. Each item has these fields. The response also carries pagination.

Show the 9 response fields and an example

The fields and an example are also on this endpoint's Markdown page.

Save a segment's LinkedIn sequence version

POST/v1/segments/{segmentId}/linkedin-sequence/versionssegment-linkedin-sequences.save-version
Permission
Campaigns edit
Rate limit
4,800 requests a minute per API key

Try it on developer.ken.so

Saves a version of the segment's own LinkedIn sequence that you can restore later. The call does not change the live steps.

Without sourceVersionId, the version is a copy of the live steps, and Kenso does not store the steps you send. With sourceVersionId, the version starts from that saved version, and a non-empty steps list replaces its steps. A connection request sent without noteMode keeps the mode of the same step and variant in that version.

Kenso checks any steps you send with the rules of PUT /v1/segments/{segmentId}/linkedin-sequence, because a restore makes them live.

Errors:

  • 400 validation_failed: a step breaks a LinkedIn sequence rule, or needs a feature that is off for the workspace.
  • 404 not_found: the segment does not exist in this workspace, or sourceVersionId is not one of its LinkedIn sequence's versions.
  • 409 conflict: another version save for this sequence is running. Retry shortly.

Requires Campaigns edit.

Request body

application/json, optional.

FieldTypeRequiredDescription
sourceVersionIdinteger (int64)optionalThe id of a saved version of this LinkedIn sequence to start from. Omit it to save a copy of the live steps.
stepsarray of ReplaceLinkedInSequenceStepRequestoptionalThe steps to store in the version, in the same shape as a LinkedIn sequence replace. Used only with sourceVersionId, where a non-empty list replaces that version's steps. Kenso checks the steps with the LinkedIn sequence rules either way.
Request
curl -X POST "https://api.ken.so/v1/segments/812/linkedin-sequence/versions" \
  -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 '{
  "sourceVersionId": 3306,
  "steps": [
    {
      "stepOrder": 1,
      "stepType": "connection_request",
      "variant": "a",
      "body": "Hi {firstName}, I work with engineering leaders on onboarding. Glad to connect.",
      "waitDays": 1,
      "anchorEmailStepOrder": 1,
      "positionInGap": 0,
      "conditionType": "none",
      "isOptional": false,
      "openProfileOnly": false,
      "waitFromCondition": false,
      "isActive": true,
      "noteMode": "template",
      "id": 9301
    },
    {
      "stepOrder": 2,
      "stepType": "message",
      "variant": "a",
      "body": "Thanks for connecting, {firstName}. Did my email about onboarding new engineers reach you?",
      "waitDays": 2,
      "anchorEmailStepOrder": 1,
      "positionInGap": 1,
      "conditionType": "accepted",
      "isOptional": false,
      "openProfileOnly": false,
      "waitFromCondition": false,
      "isActive": true,
      "id": 9302
    }
  ]
}'

Response 200

data is a LinkedInSequenceVersionSave.

Show the 3 response fields and an example

The fields and an example are also on this endpoint's Markdown page.

Get a segment's LinkedIn sequence version

GET/v1/segments/{segmentId}/linkedin-sequence/versions/{versionId}segment-linkedin-sequences.get-version
Permission
Campaigns view
Rate limit
12,000 requests a minute per API key

Try it on developer.ken.so

Returns one saved version with a copy of the LinkedIn steps as they were saved.

Errors:

  • 404 not_found: the segment does not exist in this workspace, or the version is not one of its LinkedIn sequence's versions.

Requires Campaigns view.

Parameters

NameInTypeRequiredDescription
versionIdpathinteger (int64)requiredThe version's id, from the list of versions.
Request
curl -X GET "https://api.ken.so/v1/segments/812/linkedin-sequence/versions/812" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"

Response 200

data is a LinkedInSequenceVersionDetail.

Show the 10 response fields and an example

The fields and an example are also on this endpoint's Markdown page.

Restore a segment's LinkedIn sequence version

POST/v1/segments/{segmentId}/linkedin-sequence/versions/{versionId}/restoresegment-linkedin-sequences.restore-version
Permission
Campaigns edit
Rate limit
4,800 requests a minute per API key

Try it on developer.ken.so

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

Errors:

  • 400 validation_failed: the version has no steps while the live sequence has some, a step breaks today's LinkedIn sequence rules, or a step needs a feature that is off for the workspace.
  • 404 not_found: the segment does not exist in this workspace, or the version is not one of its LinkedIn sequence's versions.
  • 409 conflict: another version save for this sequence is running. Retry shortly.

Requires Campaigns edit.

Parameters

NameInTypeRequiredDescription
versionIdpathinteger (int64)requiredThe id of the version to restore.
Request
curl -X POST "https://api.ken.so/v1/segments/812/linkedin-sequence/versions/812/restore" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"

Response 200

data is a SequenceRestore.

Show the 2 response fields and an example

The fields and an example are also on this endpoint's Markdown page.


On this page