Skip to main content

List Intake Ticket Watchers

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

Everyone on the ticket: the requester, the CCs and the watchers.

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.

Response fields (each element of data)

  • id (integer) — the ticket-scoped participant id, which is what Remove Intake Ticket Participant takes
  • user_id (integer, nullable) — the SKU.io account, when the address belongs to one
  • name (string, nullable), email (string)
  • role (string) — requester, cc or watcher
  • notify (boolean) — whether replies are mailed to them

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