PUT
Save Steps

Authorizations

Authorization
string
header
required

Interactive user session: the login JWT, sent as Authorization: Bearer <token>.

Path Parameters

sequence_id
integer
required

Body

application/json

What the builder's Save sends: the step graph, and maybe the schedule.

schedule is optional and absent means "leave the stored schedule alone", never "clear it". Every caller that predates the settings panel sends steps only, and clearing on their behalf would hand the runner a different answer than the user last chose.

steps carries no length floor on purpose. Clearing a draft down to nothing is a legitimate edit; what must not happen is losing a step that has already dispatched, and that is a question about the stored graph rather than about this payload тАФ replace_sequence_steps refuses it.

steps
SequenceStepPayload ┬╖ object[]
required
schedule
SchedulePayload ┬╖ object | null

The whole week, keyed by day name тАФ the panel's SchedulePlan.

Response

Successful Response

id
integer
required
name
string
required
status
string
required
source_type
string
required
source_id
string | null
required
config
Config ┬╖ object
required
steps
SequenceStepResponse ┬╖ object[]
required
telephony_configuration_id
integer | null
created_at
unknown
published_at
unknown