Skip to main content

Block Launch Step

POST 

/api/launch-plan/steps/:step/block

Marks an open step blocked: what it is waiting for and who it is waiting on.

Required scope: launch_plan:write

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

  • reason (required, up to 300 characters).
  • on (required) — sku (waiting on SKU.io), customer (waiting on you) or third_party (a 3PL, channel, accountant…).

While blocked the step is at risk with the reason Blocked: <reason> (waiting on SKU|you|a third party), and off track once it has been blocked more than 5 days; a step blocked 5 days or more leads the plan's health reason, and the digest lists blocked steps first. Blocking an already-blocked step replaces the reason and who but keeps when it was first blocked. Ticking the step done or signing it off clears the mark; so does it completing from data. The change is recorded in the step's activity (blocked).

Response: the full launch plan, as returned by Get Launch Plan ({data, exists: true}), with health recomputed. 422 for a step that is already done or marked not needed, or a missing / invalid reason or on. 404 for an unknown step or 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