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.
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, 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).
Response fields (each element of data)
id(integer)event(string) — one of the visible event names aboveactor(string, nullable) —SKU.io Supportfor 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 unknownfrom/to(string, nullable) — the change in customer wordingsummary(string) — a one-line sentence for the entrycreated_at(ISO-8601)
Who works the ticket is never shown: assignment and pick-up are not part of the timeline.
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
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not Found
Response Headers
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.