Skip to main content
ticket_replies

List /ticket_replies

List ticket conversation replies (the initial message is message on /tickets/{uuid}). Use filter[ticket] for one ticket's conversation and sort=created_at to read it oldest first; use filter[created_since] to poll new replies across all tickets. Each item has the author, message_text, the email envelope and attachments (download them via /tickets/{uuid}/files/{fileUuid}/content). The HTML body is only on the detail endpoint. A reply is visible when its ticket is. Response: items and pagination.

GET
/ticket_replies
Authorizationstringheaderrequired

API key (Bearer token) created in Setup → API & MCP.

querystringquery

Optional search phrase matched against the sender name and email addresses.

Minimum string length: 1
pageintegerquery

Page number (1-based).

Required range: 1 <= x
per_pageintegerquery

Number of results per page.

Required range: 1 <= x <= 50
filter[ticket]stringquery

Ticket UUIDs: the replies of these tickets.

filter[created_since]stringquery

Return only replies added at or after this ISO 8601 timestamp (e.g. 2026-09-01T00:00:00Z). Intended for polling new replies across all tickets.

filter[created_at]stringquery

Reply date range (YYYY-MM-DD - YYYY-MM-DD).

filter[uuid]stringquery

Reply UUIDs. Use it to fetch several known replies in one call.

sortstringquery

Optional sort order, comma-separated; prefix a field with - for descending (e.g. sort=-updated_at); empty values sort last. Sortable fields: created_at, email_bcc, email_cc, email_from, email_to, uuid. Default when omitted: -date,-id.

fieldsstring[]query

Optional response field paths (dot notation for nested groups, e.g. billing_address.street; array fields are returned whole). Comma-separated string is also accepted. Identifier field is always included.

Response

application/json

Search results

itemsobject[]
paginationobject
querystring