GET /v1/tickets/{ticketId}/attachments/{attachmentId}

Authentication

Send an API key as a bearer token. The key must carry the tickets.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/tickets/{ticketId}/attachments/{attachmentId} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

The file's bytes, served `Content-Disposition: attachment` with `nosniff` and a sandboxing CSP so it cannot execute in the caller's origin. ⛔ Answers **422**, not 404, when the file exists but has not passed its malware scan — a customer whose upload is quarantined must not be told their file vanished. The error code distinguishes `pending` (wait) from `infected`/`error` (never served). Requires `tickets.view`.

Parameters

Errors this endpoint can return

401 · 403 · 404 · 422 · 429