All Sequences endpoints require a valid API key. Read-only endpoints require the
sequences:read scope; write operations (update, pause, resume, stop) require sequences:write.The sequence object
Unique identifier for the sequence run.
The workspace this sequence belongs to.
The contact this sequence is targeting. May be
null if the contact record has been deleted.The template the sequence was instantiated from.
Current execution state. See Sequence statuses below.
Per-run template variable overrides merged on top of the template defaults. Keys and values are both strings; a
null value removes a variable override. Example: {"first_name": "Amélie", "company": "Acme Corp"}.The contact list that triggered this sequence, if any.
Timestamp of when the most recently executed step ran.
When the sequence was created.
When the sequence was last modified.
Sequence statuses
| Status | Description |
|---|---|
ACTIVE | The sequence is running and steps will execute on schedule. |
WAITING_FOR_LEAD | Execution is paused and will resume automatically at a future time (e.g., honoring a paused_until value set via the pause endpoint). |
WAITING_FOR_USER | A manual step is pending — the sequence is blocked until a user completes or skips the task. |
SUCCEEDED | All steps completed successfully; the sequence has finished. |
FAILED | The sequence ended due to an internal error or unrecoverable delivery failure. |
STOPPED_EARLY | The sequence was deliberately terminated via the stop endpoint. |
COMPLETED | The sequence finished all available steps (terminal, same family as SUCCEEDED). |
FOUND | An intermediate state during lead processing before the sequence is fully activated. |
REFUSED | The contact was rejected at enrollment time and the sequence never started. |
List sequences
Requires scope:
sequences:readQuery parameters
Filter by execution state. One of:
ACTIVE, WAITING_FOR_LEAD, WAITING_FOR_USER, SUCCEEDED, FAILED, STOPPED_EARLY, COMPLETED, FOUND, REFUSED.Return only sequences that were created from this template.
Return sequences created strictly after this timestamp.
Return sequences created strictly before this timestamp.
Field to sort results by. One of:
created_at, updated_at, status. Defaults to created_at.Sort direction.
asc or desc. Defaults to asc.Page number (1-indexed). Defaults to
1.Number of items per page. Between
1 and 100. Defaults to 10.Response
Array of sequence objects on this page.
Total number of sequences matching the query across all pages.
Total number of pages at the current
size.true if additional pages exist after the current one.Example — list active sequences
Get a sequence
Requires scope:
sequences:readPath parameters
The ID of the sequence to retrieve.
Example
Update a sequence
Requires scope:
sequences:writevariables dictionary — per-run template variable overrides that are substituted into outbound message content.
Path parameters
The ID of the sequence to update.
Request body
A dictionary of string key/value pairs to merge into the sequence’s runtime variables. Set a key’s value to
null to remove that override and fall back to the template default.Example
Pause a sequence
Requires scope:
sequences:writeWAITING_FOR_LEAD and will automatically resume after paused_until. Use this to hold off outreach during a scheduled sales call, a public holiday, or any other blackout window.
Path parameters
The ID of the sequence to pause.
Request body
The datetime at which the sequence should automatically resume. Must be in the future.
Example — pause until after the weekend
Resume a sequence
Requires scope:
sequences:writeWAITING_FOR_LEAD). The sequence transitions back to ACTIVE and will continue executing steps on schedule.
Path parameters
The ID of the sequence to resume.
Example
Stop a sequence
Requires scope:
sequences:writereason field signals the commercial outcome and the scope field controls whether to stop just this contact’s sequence or all active sequences in the same template that target the same company.
Path parameters
The ID of the sequence to stop.
Request body
Why the sequence is being stopped. One of:
WIN— the deal was won; no further outreach needed.LOSE— the deal was lost or the contact is not a fit.
Controls the blast radius of the stop operation. One of:
CONTACT— stop only this specific sequence run.COMPANY— stop this sequence and all other active sequences in the same template that target contacts at the same company.