Subsequences

Create Subsequence

POST /v1/sequences/{sequenceId}/subsequence

POST/v1/sequences/{sequenceId}/subsequence
POST
/v1/sequences/{sequenceId}/subsequence

Create a new subsequence under a parent sequence

Create a new subsequence under the specified parent sequence with trigger conditions, optional schedule, and optional entry delay in a single call.

Requiredtitle (1–200 chars) and conditions (min 1; all conditions use implicit AND). See the condition reference table in the Swagger schema — invalid name/operation/value combinations are rejected with a 400.

OptionalscheduleId (server assigns the account default if omitted) and firstStepRelativeDays (entry delay, min 1; omitted = no delay).

To add steps to the subsequence after creation, call POST /v1/sequences/{subsequenceId}/steps using the returned id. To read conditions back, use Get Subsequence Settings. To update, use Update Subsequence.

Authorization

x-api-key<token>

API key for Open API authentication

In: header

Request Body

application/jsonRequired

titlestring

Subsequence title. 1–200 characters.

Example: "Re-engagement Subsequence"Minimum length: 1Maximum length: 200

scheduleIdnumber

Sending schedule ID (integer). Use GET /v1/schedules to list available IDs. When omitted, the account default schedule is assigned.

Example: 58964

firstStepRelativeDaysnumber

Days after the trigger fires before the first step runs (entry delay). Minimum 1. When omitted, no delay is applied.

Example: 2Minimum: 1

conditionsarray<object>

Trigger conditions (min 1). All conditions use implicit AND logic. Each item is validated against the condition matrix — invalid name/operation/value combinations are rejected with a 400.

Example: [{"name":"Replied","operation":"is","value":false},{"conditionId":"cond-open-01","name":"Email Open Count","operation":"greater than","value":3},{"name":"Link Click","operation":"is any"}]

Path Parameters

sequenceIdstring

Hashid-encoded ID of the parent sequence.

Responses

201
Subsequence created successfully

Request

curl -X POST \
  "https://open-api.saleshandy.com/v1/sequences/{sequenceId}/subsequence" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "title": "Re-engagement Subsequence",
  "scheduleId": 58964,
  "firstStepRelativeDays": 2,
  "conditions": [
    {
      "name": "Replied",
      "operation": "is",
      "value": false
    },
    {
      "conditionId": "cond-open-01",
      "name": "Email Open Count",
      "operation": "greater than",
      "value": 3
    },
    {
      "name": "Link Click",
      "operation": "is any"
    }
  ]
}'

Response

No response body