Reopen Launch Step
POST/api/launch-plan/steps/:step/reopen
Reopens a signed-off or manually ticked step, clearing the sign-off. Reopening fulfillment_cutover_decision also resets the profile's fulfillment_cutover to undecided (with a profile_changed activity entry).
launch_plan:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
reason (required, up to 255 characters) — recorded in the step's activity.
Data-driven steps can't be reopened by hand; they reopen by themselves when the data changes (422). Response: the full launch plan, as returned by Get Launch Plan ({data, exists: true}), with dates and health recomputed.
Authentication: Requires Bearer token with the launch_plan:write scope. The user needs the launch_plan.manage permission.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.