> ## Documentation Index > Fetch the complete documentation index at: https://docs.enneo.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get report data > Returns the data for a specific report type ## OpenAPI ````yaml https://dev.enneo.dev/api/mind/docs/open-api get /report/{reportCode} openapi: 3.0.0 info: version: '1' title: enneo.MIND API description: This describes the API of enneo Mind, the main ticketing backend contact: name: enneo GmbH email: richard@enneo.ai license: name: Proprietary software url: https://enneo.ai servers: - url: https://demo.enneo.ai/api/mind description: Production server, demo client - url: https://main.enneo.dev/api/mind description: Development main branch - url: http://localhost:8005/api/mind description: Local development server security: - bearerAuth: - api - cookieAuth: - api paths: /report/{reportCode}: get: tags: - Report summary: Get report data description: Returns the data for a specific report type operationId: getReport parameters: - name: reportCode in: path required: true description: The type of report to retrieve schema: type: string enum: - openTickets - channelMix - solvedTicketsByTeam - solvedTicketsByResolution - incomingVolume - customerSurveys - telephonyLines - telephonyAgents - telephonyAiAgents - telephonyPerformance - telephonyCallInsights - telephonyLineTopPerformers - qualityAssessments example: openTickets - name: status in: query required: false description: > Filter by status. Supported values depend on the report type: - channelMix: open, closed, pending (ticket status) - telephonyAgents: all, assignedToPhone, online, onlineActive (user status categories) schema: type: string example: open - name: channel in: query required: false description: Filter by channel (only for channelMix report) schema: type: string enum: - email - portal - phone - system - chat - letter example: email - name: lastDays in: query required: false description: >- Number of days to look back (for solvedTicketsByTeam, solvedTicketsByResolution, incomingVolume, channelMix, telephonyPerformance, telephonyCallInsights, telephonyLineTopPerformers, and other telephony reports) schema: type: string enum: - '0' - '1' - '3' - '7' - '14' - '30' - '90' - '365' example: '14' - name: agent in: query required: false description: >- Filter by agent type (only for solvedTicketsByResolution, solvedTicketsByTeam, customerSurveys report) schema: type: string enum: - own - team - all example: own - name: ticketScope in: query required: false description: > Restrict the report to tickets matching the agent's configured skill tags (only for openTickets, channelMix, solvedTicketsByTeam, customerSurveys reports). - all: no skill-based restriction - skills: restrict to tickets whose routing-relevant tags overlap the agent's `actualSkills.tagIds` When the agent has no skill tags configured, `skills` behaves like `all`. schema: type: string enum: - all - skills example: all - name: teamIds in: query required: false description: >- Filter by teams (only for telephonyAgents report). Can be 'all' or comma-separated team IDs. schema: type: string example: all - name: lineIds in: query required: false description: >- Filter by telephony lines (for telephonyAgents and telephonyAiAgents reports). Can be 'all' or comma-separated line IDs. schema: type: string example: all - name: show in: query required: false description: >- Filter by user type (only for telephonyAgents report). Defaults to 'users' if not provided. schema: type: string enum: - users - all - enneo - serviceWorkers - codeExecutors - enneoPartners example: users - name: q in: query required: false description: >- Search by agent name (case-insensitive substring, only for telephonyAgents report). schema: type: string example: Alice - name: limit in: query required: false description: >- Maximum number of items to return (only for telephonyAgents report). Defaults to 1000. schema: type: integer minimum: 1 example: 50 - name: offset in: query required: false description: >- Number of items to skip for pagination (only for telephonyAgents report). Defaults to 0. schema: type: integer minimum: 0 example: 0 - name: lineId in: query required: false description: >- Filter by specific telephony line ID (for telephonyPerformance, telephonyCallInsights, telephonyLineTopPerformers reports). Required for telephonyLineTopPerformers. schema: type: string example: '11' - name: agentsType in: query required: false description: >- Filter by agent type (only for telephonyLineTopPerformers report). Defaults to 'all' if not provided. schema: type: string enum: - all - ai - human example: all - name: scorecardId in: query required: false description: Filter by scorecard base ID (only for qualityAssessments report). schema: type: string example: '1' - name: dateFrom in: query required: false description: > Start date for custom date range (only for qualityAssessments report, overrides lastDays). Format: YYYY-MM-DD schema: type: string format: date example: '2024-01-01' - name: dateTo in: query required: false description: > End date for custom date range (only for qualityAssessments report, overrides lastDays). Format: YYYY-MM-DD schema: type: string format: date example: '2024-12-31' - name: granularity in: query required: false description: > Time bucket size for time-series reports. When omitted the response is byte-identical to the pre-granularity behaviour (including the legacy 0–23 hour-of-day profile for callsAnsweredByHour). Applicable reports — hour/day/week/month: incomingVolume, telephonyPerformance, telephonyCallInsights (aiHandledVsHuman + callsAnsweredByHour timeline), telephonyAgentPerformance, telephonyAiAgentPerformance, telephonyAiAgentCallInsights. Day/week/month only (DATE column, no time-of-day): solvedTicketsByTeam, solvedTicketsByResolution. - hour: one bucket per clock-hour, keys in "YYYY-MM-DD HH:00" format; only allowed with lastDays ≤ 31 - day: one bucket per calendar day, keys in dd.mm format (legacy default) - week: one bucket per ISO week, keys in YYYY-WNN format - month: one bucket per calendar month, keys in YYYY-MM format schema: type: string enum: - hour - day - week - month example: week responses: '200': description: Successful operation content: application/json: schema: type: object properties: data: oneOf: - type: object description: For openTickets report properties: dueInMoreThan24Hours: type: integer example: 10 dueInNext24Hours: type: integer example: 5 overdue24Hours: type: integer example: 3 overdue24To48Hours: type: integer example: 2 overdueMoreThan48Hours: type: integer example: 1 totalTickets: type: integer example: 21 - type: object description: For channelMix report additionalProperties: type: integer example: email: 50 chat: 30 phone: 20 - type: object description: >- For time-based reports (solvedTicketsByTeam, solvedTicketsByResolution, incomingVolume) additionalProperties: type: object example: '2023-01-01': teamTicketsWorked: 10 ownTicketsWorked: 5 - type: object description: For customerSurveys report additionalProperties: type: integer example: '1': 2 '3': 5 '4': 8 '5': 15 - type: array description: For telephonyLines report items: type: object properties: id: type: integer description: Unique identifier for the telephony line example: 1 name: type: string example: Main Service line status: type: string enum: - active - inactive example: active liveCallsTotal: type: integer example: 38 liveCallsHuman: type: integer example: 35 liveCallsBot: type: integer example: 3 asaHumanSeconds: type: integer description: >- Average Speed of Answer for human calls in seconds example: 141 inQueueCount: type: integer example: 4 inQueueTimeSeconds: type: integer description: Average time in queue in seconds example: 31 - type: array description: >- For telephonyAgents report - returns enriched agent identity, routing state, and today's telephony metrics. items: type: object properties: agent: type: object description: Agent identity and current routing state properties: id: type: integer description: Unique identifier for the agent example: 1 name: type: string description: Full name of the agent example: Alice Anderson status: type: string description: Current profile status of the agent example: active channels: type: array description: Channels the agent is skilled for items: type: string example: - email - phone - chat callRoutingStatus: type: string description: Current call routing status example: idle chatRoutingStatus: type: string description: Current chat routing status example: idle metrics: type: object description: Today's telephony statistics for the agent properties: callsToday: type: integer description: Number of calls handled today example: 13 talkTimeSeconds: type: integer description: Total talk time in seconds today example: 1934 acwTimeSeconds: type: integer description: After Call Work time in seconds today example: 767 missedCalls: type: integer description: Number of missed calls today example: 1 - type: array description: For telephonyAiAgents report items: type: object properties: id: type: integer description: Unique identifier for the AI agent example: 1 aiAgentName: type: string description: AI agent name example: Basis-Agent callsToday: type: integer description: Number of calls handled today example: 13 talkTimeSeconds: type: integer description: Total talk time in seconds example: 1934 transferred: type: integer description: Number of calls transferred to human agents example: 1 appearance: type: object description: Visual appearance configuration properties: avatar: type: object properties: image: type: string description: Path to avatar image example: /pics/avatars/enneo_AI-Agent_10.png background: type: string description: CSS gradient for background example: >- linear-gradient(35deg, #DED8F4 20.66%, #8267CC 81.17%) - type: object description: >- For telephonyPerformance report - returns object with camelCase keys, each containing data/description/filters/summary (similar to aiPerformance) properties: answeredCalls: type: object properties: data: type: object additionalProperties: type: object properties: Answered Calls: type: integer example: '28.11': Answered Calls: 73 '29.11': Answered Calls: 75 description: type: string example: >- Number of answered calls per day in the selected period. filters: type: object summary: type: object properties: total: type: integer average: type: integer missedCalls: type: object properties: data: type: object additionalProperties: type: object properties: Missed Calls: type: integer description: type: string filters: type: object summary: type: object reachability: type: object properties: data: type: object additionalProperties: type: object properties: Reachability: type: integer description: type: string filters: type: object summary: type: object asa: type: object properties: data: type: object additionalProperties: type: object properties: ASA: type: integer description: type: string filters: type: object summary: type: object aht: type: object properties: data: type: object additionalProperties: type: object properties: AHT: type: integer description: type: string filters: type: object summary: type: object sla: type: object properties: data: type: object additionalProperties: type: object properties: SLA: type: integer description: type: string filters: type: object summary: type: object - type: object description: >- For telephonyCallInsights report - returns object with 3 data items (aiHandledVsHuman, detectedIntents, callsAnsweredByHour) properties: aiHandledVsHuman: type: object description: Daily breakdown of AI vs Human handled calls properties: data: type: object additionalProperties: type: object properties: Human: type: integer AI: type: integer example: '28.11': Human: 52 AI: 23 '29.11': Human: 48 AI: 19 description: type: string example: >- Daily breakdown of calls handled by AI versus human agents in the selected period. filters: type: object summary: type: object properties: totalHuman: type: integer totalAI: type: integer aiPercentage: type: integer detectedIntents: type: object description: >- Distribution of detected customer intents (pie chart data) properties: data: type: object additionalProperties: type: integer example: Allgemein: 25 Mako: 30 Rechnung: 13 Lorem: 23 Ipsum: 9 description: type: string example: >- Distribution of detected customer intents across all calls in the selected period. filters: type: object summary: type: object properties: total: type: integer percentages: type: object additionalProperties: type: integer counts: type: object description: >- Absolute per-intent call counts (raw numbers before percentage conversion) additionalProperties: type: integer callsAnsweredByHour: type: object description: > Breakdown of call outcomes by hour-of-day or chronological timeline. Without granularity: fixed 0–23 slots (hour-of-day aggregate, legacy). With granularity: chronological timeline buckets keyed by the granularity format (e.g. "2026-06-02 14:00" for hour, "02.06" for day, "2026-W23" for week). properties: data: type: object additionalProperties: type: object properties: AI Bot finished: type: integer Handed over to human: type: integer Declined/Missed: type: integer Short call (<10s): type: integer example: '9': AI Bot finished: 12 Handed over to human: 18 Declined/Missed: 4 Short call (<10s): 2 2026-06-02 09:00: AI Bot finished: 12 Handed over to human: 18 Declined/Missed: 4 Short call (<10s): 2 description: type: string example: >- Hourly breakdown of call outcomes showing how calls were handled throughout the day. filters: type: object summary: type: object properties: aiBotFinished: type: integer aiBotHandedOver: type: integer transferredDropped: type: integer customerDeclinedDPA: type: integer shortCall: type: integer description: type: string description: Description of what the report shows example: >- Tickets in status 'open', broken down by due date compared to the current time. summary: type: object description: >- Summary statistics for the report (optional, only for some reports) oneOf: - type: object description: For channelMix report properties: title: type: string example: Open tickets amount: type: integer example: 63 description: type: string example: '' - type: object description: For solvedTicketsByTeam report properties: ownAmount: type: integer example: 10 teamAmount: type: integer example: 15 totalAmount: type: integer example: 8 amount: type: integer example: 33 - type: object description: For customerSurveys report properties: totalShown: type: integer description: Total number of surveys sent example: 100 responseRate: type: number description: Response rate as percentage example: 85.5 currentScale: type: integer description: Current scale setting used for normalization example: 5 - type: object description: For telephonyLines report properties: currentLiveCalls: type: integer description: >- Total number of current live calls across all lines example: 59 currentInQueue: type: integer description: >- Total number of calls currently in queue across all lines example: 5 - type: object description: For telephonyAgents report properties: availableAgents: type: integer description: Number of agents currently available example: 3 onlineAgents: type: integer description: Total number of agents online example: 15 callsToday: type: integer description: >- Total number of calls handled today across all agents example: 49 missedCalls: type: integer description: Total number of missed calls across all agents example: 16 - type: object description: For telephonyAiAgents report properties: totalAiAgents: type: integer description: Total number of AI agents example: 3 callsToday: type: integer description: >- Total number of calls handled today across all AI agents example: 40 transferred: type: integer description: Total number of calls transferred to human agents example: 4 total: type: integer description: >- Total number of items after filters and search, before pagination (only present for reports that support pagination, e.g. telephonyAgents). example: 42 filters: type: object description: The filters that were applied to generate this report example: lastDays: 14 agent: own '400': description: Invalid filter parameters content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Unauthorized '500': description: Internal error content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: Error: type: object description: Data format of Enneo error messages properties: error: type: string example: Contract 121 could not be processed description: Readable error message that should be shown to the user details: type: string example: >- Uncatched null point exception in testFunction() in /app/src/file:212 description: Not easily readable error message that is for the developer txId: type: string example: c916167c94 description: >- Internal transaction id. Useful for debugging. Corresponds to the OpenTelemetry trace ID. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT-based authentication x-scopes: api: Full access to the API cookieAuth: type: apiKey in: cookie name: connect.sid description: Cookie-based authentication x-scopes: api: Full access to the API ````