customer_service

Get Ticket Attachment

Stream one attachment to the browser.

Customers send screenshots of what went wrong, photos and PDFs, and every one of those has to reach the person answering the ticket. The bytes live in Chatwoot; this is the only way they reach a browser. Company OS proxies them so a vendor host never appears in our markup and the file stays behind our own permissions rather than whatever a signed vendor link happens to allow.

Keyed by TICKET, not by Chatwoot conversation: the browser should not have to know a vendor's id scheme to open a photo, and department scoping is a property of the ticket. A consumer agent cannot read a government attachment by guessing an id.

get/api/cs/tickets/{ticket_id}/attachments/{attachment_id}

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/cs/tickets/{ticket_id}/attachments/{attachment_id}
  • Auth: none declared

Path parameters

ticket_idstring uuid required
attachment_idstring uuid required

Query parameters

downloadboolean

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.