Inline Support Attachment (signed URL)
GET/api/support/attachments/:attachment/inline
Serves a ticket attachment for a signed, expiring URL — no bearer token, no session: the signature is the whole authorisation. These URLs are never built by hand; every attachment in a message resource (GET /api/support/tickets/:ticket/messages, GET /api/support/agent/tickets/:ticket/messages) carries its own as url (inline) and download_url (download), valid for 2 hours. A message that arrived by email also has html_source: "email", its body_html rewritten so each cid: image source points at the matching attachment's url, and inline_attachment_ids listing the attachments shown that way.
Images (image/png, image/jpeg, image/gif, image/webp, image/bmp, image/avif) are served inline with their media type. Anything else — including SVG and HTML, which would execute in the app's origin — is always served as Content-Disposition: attachment under its original filename, whatever download says.
Available on the pod that holds the file (production); a remote intake pod answers 404. Central — no X-Tenant-Id.
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
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
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.