Skip to main content

List Intake Ticket Events

GET 
/api/support/intake/tickets/:ticket/events

Returns the customer-visible timeline of a ticket, oldest first, as a plain array (no pagination). Only the events a customer may see are included; everything internal to the desk is left out.

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.

Events you will see: created, status_changed, reopened, assigned, unassigned, linked (only when the link is a release — "a fix for this ticket shipped"), rated, merged, split.

Response fields (each element of data)

  • id (integer)
  • event (string) — one of the visible event names above
  • actor (string, nullable) — the first name of the person who made the change; SKU.io Support for changes the desk made itself; null when unknown
  • from / to (string, nullable) — the change in customer wording
  • summary (string) — a one-line sentence for the entry
  • created_at (ISO-8601)

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.

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