Hide Feature
POST/api/feature-adoption/preferences
Marks one feature (feature_key) or every not-yet-used feature of a group (group: marketplaces, storefronts, 3pl, accounting) as not relevant to the business. A group never hides features that are active; those are returned in kept_active. skipped lists group members left untouched (lapsed, unavailable or already hidden). note is required for other_tool and didnt_work (max 500). A hidden "maybe_later" feature returns automatically after 90 days, and any hidden feature returns automatically once it is used.
reports:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Requires the feature_adoption.manage permission.
Authentication: Requires Bearer token with the reports scope.
Each feature's preference (null unless the feature is marked "Not for us") carries reason, reason_label, note, marked_at, marked_by (user id) and marked_by_name — the display name of whoever marked it: "SKU.io support" when marked by SKU.io staff, "Former user" when the user no longer exists.
Request
Responses
- 200
- 401
- 403
- 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
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.