Skip to main content

Resolve Intake Ticket

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

Marks the ticket resolved on behalf of the person in the identity headers. Once resolved it can be rated and drops out of the default ticket list unless closed tickets are included. The response is the updated ticket; both SLA clocks now report met or breached depending on whether the first response and the resolution landed before their due dates.

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.

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​

OK

Response Headers
    Content-Type