Skip to main content

List Support Ticket Events

GET 
/api/support/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 support desk is left out.

Required scope: support:read

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

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.

Events that are never shown here: priority_changed, type_changed, visibility_changed, group_changed, replied, noted, watcher_added, watcher_removed, unlinked, tags_changed, tenant_changed, sla_breached, sla_warning, sla_paused, sla_resumed, ai_triaged, snoozed, unsnoozed, mentioned, follow_up_changed, notified, rule_applied, and linked events for anything other than a release. Replies are read from List Support Ticket Messages instead.

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 made by the desk itself (automation, release loop); null when unknown
  • from / to (string, nullable) — the change in customer wording. Status values are the customer labels (Open, Being worked on, Waiting on you, Fix scheduled for release, Resolved, Closed); assignment values are the agent's first name; a release link reads release; a rating is the score (1–5); merge/split carry the other ticket's id
  • summary (string) — a one-line sentence for the entry, e.g. Ticket opened, Status changed to Resolved, Assigned to Priya, Fix released, Rated 5/5, Merged into #2478, Split from #2451
  • created_at (ISO-8601)

A ticket belonging to another tenant returns 404. A requester-only ticket you did not raise and were not added to returns 403.

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​

OK

Response Headers
    Content-Type