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, linked (only when the link is a release — "a fix for this ticket shipped"), rated, merged, split, stage_changed (the work stage moved — "Now: Investigating"), progress_posted (a progress update; to and summary carry its text), category_changed (the ticket's category was set or corrected; from / to read like Amazon · How-to question, and an automatic suggestion is credited to SKU.io Support).

Events that are never shown here: assigned, unassigned, picked_up, human_requested, 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, released, requester_linked, approval_requested, approval_decided, handed_back, ai_paused, ai_resumed, ai_stop_requested, ai_stopped, ai_instructed, ai_disabled, ai_enabled, 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) — SKU.io Support for every change the support team made (whoever on the team made it); the first name of the person on your side for your own changes; 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); 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, Rated 5/5, Merged into #2478, Split from #2451
  • created_at (ISO-8601)

Who works the ticket is never shown: assignment and pick-up are not part of the timeline.

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