Mark Success Plan Goal Met
POST/api/success-plan/goals/:goal/met
Marks a goal with no target as met ("We got there"). Goals with a target are marked met by SKU.io when a reading reaches it, so they answer 422 goal_has_target. The goal-met result is logged in the story, and the goal becomes eligible for the goal-met response (see Respond to Goal Met).
success_plan:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token with the success_plan:write scope. The user must hold the success_plan.manage permission.
Body (everything optional, under met or at the top level):
met.value(number): the value reached.met.as_of(dateY-m-d, not in the future).met.source_note(string, max 255).met.evidence(string):document,system_exportorestimate.met.attachment_ids(integer array, max 10): only withdocumentorsystem_export.
Returns the goal with status: met and met_at.
409 goal_busy: SKU.io was measuring this goal and did not finish in time; nothing was saved, so retry shortly.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 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
Response Headers
Conflict
Response Headers
Unprocessable Entity
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.