Skip to main content

Get Intake Ticket

GET 

/api/support/intake/tickets/:ticket

Returns one ticket with its watchers and the links a customer may see. The response is the production customer ticket, field for field, plus environment, origin_tenant_id and origin_host.

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.

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 — whichever environment raised them. A ticket outside that set is reported as not found, never as forbidden, so a ticket id can never be probed from another environment.

first_response_sla_status and resolution_sla_status report the ticket's two SLA clocks: one of on_track, breaching_soon, breached, paused (the ticket is waiting on the customer, so neither clock warns) or met. merged_into is {id, number} once the ticket has been merged into another, otherwise null.

work — how far along the ticket is, in customer wording (null only on a ticket raised before work tracking existed). It never says who works the ticket — the support team is always "SKU.io Support":

  • picked_up_at (ISO-8601, nullable) — when SKU.io Support first picked the ticket up
  • stage (string) — one of: received, investigating, fixing, waiting_on_you, resolved (a ticket SKU.io Support has started on reads investigating — the customer is never told it was picked up, or by whom); stage_label (string) — Received, Picked up, Investigating, Working on a fix, Waiting on you, Resolved
  • working_now (boolean) and active_until (ISO-8601, nullable) — SKU.io Support is actively working the ticket right now
  • progress_text (string, nullable) and progress_at (ISO-8601, nullable) — the latest progress update

Who works the ticket, the internal working phase, the stale flag and approval cards are never part of the customer view.

category — what the ticket is about and why it was raised:

  • feature_key (string, nullable) — a key from the categories list (a SKU.io feature, platform.other or none); null while uncategorised. feature_label is its display name
  • area / area_label (string, nullable) — the product area of that feature (null for none or while uncategorised)
  • cause (string, nullable) — one of: how_to, configuration, defect, third_party, request, billing, data_process, other. cause_label is its display name
  • source (string, nullable) — who set it: ai (suggested automatically when the ticket was triaged), customer (someone on the account) or agent (SKU.io Support); source_label is the same in customer wording
  • suspected_defect (boolean) — an automatic check suspected a bug that nobody has confirmed yet. It is never counted as a defect; only SKU.io Support (or an engineering link) makes a ticket a defect
  • locked (boolean) — true once SKU.io Support set the category; the customer can no longer change it
  • set_at (ISO-8601, nullable) — when it was last set

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