Developers
Tickets9

List ticket replies

GET/support/tickets/{ticket_id}/replies

Returns the ticket conversation in chronological order, oldest message first, using cursor-based pagination. The collection includes messages from the user and from the support team.

Authorization

AuthorizationBearer <token>

Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.

In: header

Path Parameters

ticket_id*string

Public ID of the ticket, prefixed with tkt_.

Header Parameters

X-Client-Request-Id?string

Optional client-generated identifier of the request, up to 64 characters from [A-Za-z0-9._-]. Echoed back in the response and recorded in the request log; it never replaces the server-generated X-Request-Id.

Lengthlength <= 64

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/support/tickets/string/replies"
{  "data": [    {      "attachments": [        {          "file_id": "string",          "name": "string",          "url": "string"        }      ],      "author": {        "id": "string",        "kind": "user"      },      "created_at": "2019-08-24T14:15:22Z",      "id": "string",      "object": "ticket_reply",      "revision": "string",      "text": "string",      "updated_at": "2019-08-24T14:15:22Z"    }  ],  "page": {    "limit": 1,    "next_cursor": "string",    "prev_cursor": "string"  }}

Update a ticket PATCH

Updates the subject or support department of a ticket, or closes and reopens it through `status`. Changing `status` requires the `tickets.close` permission in addition to `tickets.update`. Send the `ETag` returned by the retrieve operation in the `If-Match` header to avoid overwriting a newer version.

Create a ticket reply POST

Adds a reply to the ticket conversation on behalf of the support team. The reply is attributed to the credential that made the request (`author.kind` is `credential`).