Remove Intake Ticket Watcher
DELETE/api/support/intake/tickets/:ticket/watchers
Removes a watcher or CC from the ticket by email address, for the same reason they are added by address: an id from your environment names a different person on the desk. Send the address as the email query parameter or as a JSON body — both are read.
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.
It removes either shape of participant: a colleague with a SKU.io account and a bare CC address alike. The requester cannot be removed from their own ticket (422). An address nobody on the ticket holds is a 404.
Parameters
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
- 204
- 401
- 403
- 404
- 422
- 429
No Content
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.