List Support Ticket Categories
GET/api/support/categories
Lists the values a ticket's category can take, for a category picker.
support:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Response fields (data)
features[]— every feature a ticket can be about, grouped by product area in display order:key,label,area,area_label. The list ends with two catch-alls:platform.other(about SKU.io, but no listed feature fits) andnone(not product-related, e.g. an account question; itsareais null)causes[]— why a ticket was raised:value,label. One of how_to, configuration, defect, third_party, request, billing, data_process, other
The feature list follows SKU.io's feature catalog, so it can grow between releases. When a feature is retired, tickets that carried it move to its successor (or platform.other) and the change appears on their timeline. The example below is abbreviated; the live list has around 90 features.
Authentication: Bearer token with the support:read scope, or an authenticated session. Customer endpoints run in tenant context — send the X-Tenant-Id header or call from a tenant subdomain.
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthorized
Response Headers
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.
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.