Skip to main content

Sign Off Launch Step

POST 

/api/launch-plan/steps/:step/sign-off

Signs off a checkpoint step (completion: signoff) with a note, as the calling person. Signing off the go_live checkpoint marks the plan launched.

Required scope: launch_plan:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

note (required, up to 5000 characters).

choice — required for the fulfillment_cutover_decision checkpoint (the step whose choice_required is true), and refused (422) on every other step: A (SKU routes orders from day 1) or B (phased). It is stored as the profile's fulfillment_cutover (with a profile_changed activity entry) and the plan's steps re-resolve — under B, routing_enabled becomes a sign-off checkpoint.

422 when choice is missing or not A/B on the cutover decision, when the step is not a checkpoint, is marked not needed, is only available on the production account, or still has open dependencies (the message lists them). The beta_signoff checkpoint waits on every step of the validate phase, custom steps included. A sign-off is a person's decision, so personal access tokens get 403. Response: the full launch plan, as returned by Get Launch Plan (\{data, exists: true\}), with dates and health recomputed.

Signing off also clears the step's blocked mark.

Authentication: Requires Bearer token with the launch_plan:write scope. The user needs the launch_plan.manage permission.

Request​

Responses​

OK

Response Headers
    Content-Type