Get ticket_details

Technical field used as primary key of the model.

Unique identifier for the ticket.

URL link to the ticket in the Tidio panel.

Subject of the ticket.

Unique identifier for the contact.

Priority of the ticket.

Status of the ticket.

Unique identifier of the agent assigned to the ticket. Important: once the ticket is being marked as solved the assignment is being reset to null, that’s why for reporting purposes we recommend using last_involved_operator_id column.

Unique identifier of the agent that sent last message in the ticket.

Unique identifier of the department assigned to the ticket.

Timestamp indicating when the ticket was created.

Source where the ticket was created.

List of tags assigned to the ticket.

Timestamp indicating when the last message in the ticket was sent, if the ticket has status 'solved'.

Indicator of whether a ticket has been routed to a Lyro AI agent to attempt to generate a response to a question from the ticket. The attempt may end up generating a response (ind_has_ai_assistant_actor = 1) otherwise (ind_has_ai_assistant_actor = 0)

Indicator of whether Lyro AI Agent generated a response to a question from the ticket.

List of custom fields assigned to the ticket.

Technical timestamp (UTC, NTZ)

Filtering Columns

Ordering

Limiting and Pagination

Maximum rows to return. Pre-filled with 100 to keep the request fast. The API applies no implicit limit -- an unbounded query against a large table exceeds the 25s statement timeout and returns 408, so raise this in steps and page rather than clearing it.

Limiting and Pagination

Limiting and Pagination

Preference