Skip to main content

Download Intake Ticket Attachment

GET 
/api/support/intake/attachments/:attachment/download

Returns a file attached to a ticket message. The attachment must hang off a public message of a ticket this caller can see — files on internal notes, files on a ticket outside the caller's scope, and files no longer attached to any message all answer 404 exactly as a non-existent attachment does.

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.

Two shapes of success, and a client must follow both: when the desk's storage can sign a link the response is a 302 redirect to a short-lived URL, so the bytes travel from the customer's browser straight to storage and never pass through your environment; otherwise the file is streamed (Content-Type is the attachment's stored media type, with Content-Disposition: attachment and its original filename). Neither is JSON.

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
    Content-Disposition