Skip to main content
Talk to salesStart

Set sequence status

Set sequence status to ACTIVE, PAUSED, or ARCHIVED.

PATCH/api/sequences/{sequence_id}/status
HTTP referenceScope sequences:runUpdated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

Changing status to ACTIVE can admit runnable enrollments and synchronize provider/runtime state. Changing to PAUSED or ARCHIVED drains/pause sequence enrollments and open work. Status transitions are state-changing operations.

In Command Center, Approve for me may authorize activation automatically, while Ask for approval still requires confirmation. Enrollment and combined launch-and-enroll actions remain sensitive under Approve for me, including manual-only or review-only enrollment. Run without asking retains its existing authority. These native agent rules do not add an approval step to HTTP or CLI calls: those retain explicit authenticated invocation, sequences:run, sender authorization and readiness checks.

Activation readiness

  • Personal delivery checks inbox readiness for the resolved actor user.
  • Bulk delivery checks provider configuration/campaign readiness.

Path parameters

  • sequence_idrequired

    string

    Sequence ID.

Query parameters

  • actorUserId · optional

    string

    Optional actor override; controls personal inbox readiness checks.

Body parameters

  • statusrequired

    string

    One of ACTIVE, PAUSED, ARCHIVED.

Errors

StatusMeaning
400Invalid status or actor.
401Invalid API key or missing auth.
403Missing sequences:run scope.
404Sequence not found.
409Delivery not ready for activation (for example inbox/provider not configured).

Docs