Skip to main content

Update Launch Plan

PATCH 
/api/launch-plan

Changes plan settings. Send only the fields to change:

  • target_launch_on — Y-m-d or null (null leaves the plan unscheduled). Can't be in the past unless the plan is launched.
  • status — active | paused | launched | archived. A paused plan is not re-evaluated and sends no digests; archiving frees the account for a new or imported plan (until then the archived plan can still be read and resumed with active; once replaced it is kept as history). launched is accepted only once the go_live checkpoint is signed off (signing it off is what launches a plan); otherwise 422 "Sign off Go live to mark the plan launched." active on a plan whose go_live is signed off (resuming a paused or archived launched plan) resolves to launched — read status from the response.
  • digest_enabled — boolean, the weekly email digest.
  • tolerance_days — integer 0–60, days a milestone's pace forecast may run past its due date before it is off track (default 7). Only SKU.io support can change it; other callers get 403.
Required scope: launch_plan:write

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

Target and status changes are recorded in the plan's activity. Response: the full launch plan, as returned by Get Launch Plan ({data, exists: true}), with dates and health recomputed. 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​

OK

Response Headers
    Content-Type