Reports API

This article and the rest of the API documentation in this section are written for a technical audience — integrators and developers connecting external systems to Tickiti. Familiarity with HTTP, REST, JSON and bearer-token authentication is assumed.

The Reports API returns the same analytics the Reports screens render, as JSON — useful for feeding an external dashboard. It is read-only. Every endpoint runs as the token’s owner and is gated by the reports:read ability plus the owner’s admin role and the reports plan feature.

Conventions

All endpoints are POST and JSON. Each report takes a date window and optional scope:

date_from, date_to — required (ISO dates).
queue_id — optional; omit for all tracked queues.
group_by — day | week | month (volumes and response-times only).

Responses are chart-ready (labels + one or more value series). Use /meta to discover the queues you can filter by.

Endpoints

Method & path	Ability	Purpose
POST /api/v1/reports/meta	reports:read	Queues available as report filters
POST /api/v1/reports/resolutions	reports:read	Closed-ticket breakdown by resolution category
POST /api/v1/reports/volumes	reports:read	Tickets created per period
POST /api/v1/reports/response-times	reports:read	First-response and time-to-close (hours) per period
POST /api/v1/reports/agent-activity	reports:read	Material staff responses per agent