Retrieve a ticket reply
/support/tickets/{ticket_id}/replies/{reply_id}Retrieves a single message from the ticket conversation. The message must belong to the ticket in the path; otherwise the API returns 404 Not Found.
The response includes an ETag representing the current revision. Send this value in the If-Match header when updating the reply to avoid overwriting a newer version.
Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.
In: header
Path Parameters
Header Parameters
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.
length <= 64Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/support/tickets/string/replies/string"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`).
Update a ticket reply PATCH
Corrects the text of a support team reply. The original creation time of the reply is preserved, and the user is not notified again. Only replies written by the support team (`author.kind` of `admin` or `credential`) can be edited. Attempting to edit any other message returns `403` with the `permission_denied` error code and `details[].field` set to `author.kind`. Send the `ETag` returned by the retrieve operation in the `If-Match` header to avoid overwriting a newer version.