---
title: "Get agent_thread_intent_statistics_daily"
method: GET
path: "/agent_thread_intent_statistics_daily"
tags: ["Agent thread intent statistics daily"]
---

# Get agent_thread_intent_statistics_daily

`GET /agent_thread_intent_statistics_daily`

## Request

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

This endpoint provides you with data on human agent thread level in daily resolution.

## Query parameters

- `_unique_id` string
- `period_date` string
- `thread_intent` string
- `cnt_threads_with_intent` 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: Identifier of the project to which the thread belongs.
  - `period_date` string, date: The date corresponding to the information in the row.
  - `thread_intent` string: Identified intent of the thread.
  - `cnt_threads_with_intent` number: Number of threads with the given intent.
  - `_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)