Skip to main content

Add Custom Launch Step

POST 
/api/launch-plan/steps

Adds a one-off step to the plan.

  • title (required, up to 200 characters).
  • phase (required) — pre_kickoff, foundation, connect_data, catalog, validate, go_live or post_launch.
  • milestone (required) — the milestone it gates: kickoff, foundation_ready, data_connected, catalog_ready, beta_signoff, go_live, hypercare_done, accounting_live or first_month_end.
  • depends_on (optional) — step keys it waits for. Unknown keys and loops are rejected with 422. A validate-phase step is itself waited on by the beta_signoff checkpoint, so it cannot depend on beta_signoff (a loop).
  • size (optional) — S, M or L (default M). Sending effort_hours is refused (422 "Effort is now a size: S, M or L.").
  • owner_user_id (optional) — a user on this account. Anyone given a step who is not yet a plan member is added as a member (no roles, not a watcher) so they receive the weekly digest.
  • completion (required) — manual (ticked done) or signoff (signed off with a note).
  • why (optional, up to 1000 characters).
Required scope: launch_plan:write

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

A plan holds at most 150 steps. Response 201 with the full launch plan. 404 {exists: false, message} when the account has no plan.

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

Request​

Responses​

Created

Response Headers
    Content-Type