Update Sharing Consent

PUT 
/api/success-plan/consent

Changes sharing consent. Every change is kept in the history and logged in the story. Setting no revokes approved drafts that are not yet published and flags published ones for SKU.io to take down.

Required scope: success_plan:write

Grant 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:

• status (string, required): open, ask_later or no.
• permissions.name_company (boolean): the write-up may name the company.
• permissions.use_figures (boolean): it may use your figures.
• permissions.name_person (boolean): it may name the person quoted.
• note (string, max 255).

Permissions are kept only with open; any not sent are false. Returns the consent and history, as Get Sharing Consent.

Request

Responses

200

OK

Response Headers

Content-Type

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

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.

404

Not Found

Response Headers

Content-Type

422

Unprocessable Entity

Response Headers

Content-Type

429

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.