Skip to main content

Add Intake Ticket Watcher

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

Adds a watcher to the ticket, who is then notified of new replies.

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.

By address only. Unlike the production customer endpoint, this one takes no user_id: a colleague picked on your environment has an id that belongs to that environment's own accounts and would name a different person on the desk. The address is the identity — production links it to a SKU.io account when one holds it, and keeps it as a plain CC address when none does.

Request body

  • email (required, string, a valid email address, max 255)

If the ticket was merged into another, the request is refused with a 422 whose merged_into (id, number) names the live ticket — send the action there instead.

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​

Created

Response Headers
    Content-Type