Accept Launch Plan Suggestion
POST/api/launch-plan/suggestions/:suggestion/accept
Applies a pending suggestion the same way a person would: a profile_change updates the profile (list fields gain the value; steps for newly included modules are added), a custom_step adds a custom step (owner defaulted from its role). The suggestion becomes accepted.
launch_plan:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Response: {data: <suggestion>, plan: <launch plan>}. 422 when the suggestion was already decided or no longer applies; 404 for an unknown id.
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.