Skip to main content

Update Intake Ticket Category

PATCH 
/api/support/intake/tickets/:ticket/category

Corrects what a ticket is about, on behalf of the person in X-Support-Requester-Email — the same rules as Update Support Ticket Category on production: the correction is recorded as source: customer, an automatic pass never overwrites it, and once SKU.io Support has set the category (locked: true) the request is refused with 409. Every change is added to the ticket's timeline as category_changed.

Environment intake token

Called by another SKU environment (beta, demo, dev) on behalf of its users: authenticate with that environment's intake token and the origin headers described below — not with a Personal Access Token or a session.

Request body

  • feature_key (string, required) — a key from the categories list: a SKU.io feature, platform.other (about SKU.io, but no listed feature fits) or none (not product-related)
  • cause (string, required) — one of: how_to, configuration, defect, third_party, request, billing, data_process, other

The response is the updated ticket (the same shape as Get Intake Ticket).

What this caller can see: the mapped production tenant's organisation-wide tickets, plus every ticket raised from the address in X-Support-Requester-Email. A ticket outside that set is reported as not found.

Authentication: the environment token as Authorization: Bearer, plus the X-Support-* identity headers described on the Intake folder. There is no session and no tenant context. An unknown token, or a token presented with another environment, is refused with 403; incomplete identity headers are 422.

Request​

Responses​

OK

Response Headers
    Content-Type