---
title: "Get ticket_details"
method: GET
path: "/ticket_details"
tags: ["Ticket details"]
---

# Get ticket_details

`GET /ticket_details`

## Request

- Base URL: `https://taa.data.tidio.com`
- URL: `https://taa.data.tidio.com/ticket_details`
- Auth: API key in header `X-Tidio-Openapi-Client-Id` and API key in header `X-Tidio-Openapi-Client-Secret`

Raw data for tickets. Does not include deleted and spam tickets.

## Query parameters

- `_unique_id` string
- `ticket_id` string
- `ticket_link` string
- `subject` string
- `contact_id` string
- `priority` string
- `status` string
- `assigned_agent_id` string
- `last_involved_agent_id` string
- `assigned_department_id` string
- `created_at` string
- `source` string
- `tags` string
- `solved_at` string
- `ind_ai_assistant_involved` string
- `ind_has_ai_assistant_actor` string
- `ticket_custom_fields` string
- `_updated_at` string
- `select` string
- `order` string
- `offset` string
- `limit` string, required

## Headers

- `Range` string
- `Range-Unit` string
- `Prefer` 'count=none'

## Response `200`

OK

- object[]
  - `_unique_id` number: Technical field used as primary key of the model.
  - `project_id` number: Unique identifier for the project.
  - `ticket_id` number: Unique identifier for the ticket.
  - `ticket_link` string: URL link to the ticket in the Tidio panel.
  - `subject` string: Subject of the ticket.
  - `contact_id` number: Unique identifier for the contact.
  - `priority` string: Priority of the ticket.
  - `status` string: Status of the ticket.
  - `assigned_agent_id` number: 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.
  - `last_involved_agent_id` number: Unique identifier of the agent that sent last message in the ticket.
  - `assigned_department_id` number: Unique identifier of the department assigned to the ticket.
  - `created_at` string, date-time: Timestamp indicating when the ticket was created.
  - `source` string: Source where the ticket was created.
  - `tags` string: List of tags assigned to the ticket.
  - `solved_at` string, date-time: Timestamp indicating when the last message in the ticket was sent, if the ticket has status 'solved'.
  - `ind_ai_assistant_involved` number: 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)
  - `ind_has_ai_assistant_actor` number: Indicator of whether Lyro AI Agent generated a response to a question from the ticket.
  - `_updated_at` string, date-time: Technical timestamp (UTC, NTZ)

## Other responses

- `206`: Partial Content
- `408`: Request Timeout. The query took longer than the database's 25s statement limit -- almost always an unbounded read of a large table. Add a `limit`, narrow the date filter, or page with `Range`/keyset instead of scanning the whole table. `Prefer: count=exact` also forces a full scan; use `count=planned` on the large tables.

---

[API](https://skmtc.dev/tidio/apis/tidio-analytics-api.md) - [All operations](https://skmtc.dev/tidio/apis/tidio-analytics-api/llms.txt) - [OpenAPI document](https://skmtc.dev/tidio/apis/tidio-analytics-api/revisions/960021ed741c?raw)