REST API: analytics and activity

Analytics endpoints expose dashboard-aligned aggregates for statistics, daily trends, sentiment, feedback, confidence, retrieval modes, geography, low-confidence responses, and escalations. Treat these as reporting data with the filters and date semantics documented in the generated reference. A date-only dateTo is inclusive through the UTC end of that day; timestamp inputs need an explicit time zone, and reversed ranges are validation errors.

Exports are asynchronous: create an export, retain its identifier, and poll that resource at a measured interval. Activity sessions have their own pagination and message detail routes, so do not apply a generic analytics cursor assumption. Audio URLs are retrieved per message, and session deletion—single or bulk—needs an explicit retention decision before execution.

Keep reporting jobs read-scoped where possible, minimize access to individual messages, and separate dashboard metric interpretation from a promise about answer quality. Use rate-limit headers and backoff for scheduled exports or large activity reviews.