---
title: "Changes to Create campaign subsequence"
method: POST
path: "/api/v2/subsequences"
---

# Changes to Create campaign subsequence

`POST /api/v2/subsequences`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 1 of 12 revisions.

- **2026-11-03** `c781051105a8`: 13 breaking, 6 warning, 14 info

## Changes

- **2026-11-03** `c781051105a8`: 13 breaking, 6 warning, 14 info
  - added 'contains' constraint to the request property `sequences/items/steps/items/variants`
  - removed the enum value `-1.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `-2.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `-3.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `-4.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `0.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `1.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `2.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `3.00` of the request property `conditions/crm_status/items/`
  - removed the enum value `4.00` of the request property `conditions/crm_status/items/`
  - the `sequences/items/steps/items/variants` request property's minItems was increased to `1`
  - the response property `sequences` became optional for the status `200`
  - the response property `subsequence_schedule` became optional for the status `200`
  - the `conditions/crm_status/items/` request property's max was set to `30000.00`
  - the `sequences/items/steps/items/delay` request property's max was set to `527040.00`
  - the `sequences/items/steps/items/pre_delay` request property's max was set to `527040.00`
  - the `conditions/crm_status/items/` request property's min was set to `-30000.00`
  - the `sequences/items/steps/items/delay` request property's min was set to `0.00`
  - the `sequences/items/steps/items/pre_delay` request property's min was set to `0.00`
  - added the new optional request property `auto_variant_select`
  - the request property `sequences` became optional
  - the request property `subsequence_schedule` became optional
  - added the optional property `auto_variant_select` to the response with the `200` status
  - added 'contains' constraint to the `sequences/items/steps/items/variants` response property for the status `200`
  - removed the `-1.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `-2.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `-3.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `-4.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `0.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `1.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `2.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `3.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`
  - removed the `4.00` enum value from the `conditions/crm_status/items/` response property for the response status `200`

---

[Operation](https://skmtc.dev/instantly/apis/api-explorer/docs/api/v2/subsequences/post.md) - [API](https://skmtc.dev/instantly/apis/api-explorer.md) - [Page](https://skmtc.dev/instantly/apis/api-explorer/changes/api/v2/subsequences/post)
