> ## Documentation Index > Fetch the complete documentation index at: https://docs.ringg.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > To search or read these docs, connect the Ringg docs MCP server at https://docs.ringg.ai/mcp (no key needed; tools search_ringg_ai and query_docs_filesystem_ringg_ai) instead of browsing pages one by one. Setup for each client: https://docs.ringg.ai/resources/mcp-server/docs-mcp-server/mcp-for-ai-assistants.md > The dashboard labels agents "Assistants"; these docs say "agent". Both mean the same object, identified by agent_id. > API base URL: https://prod-api.ringg.ai/ca/api/v0. Send the workspace API key in the X-API-KEY header, from server-side code only. > Placing a call dials a real phone number and spends credits. Confirm the number with the user before calling. > To act on a Ringg workspace (place calls, edit agents, read transcripts), use the separate Ringg workspace MCP server at https://mcp.ringg.ai/mcp: https://docs.ringg.ai/resources/mcp-server/workspace-mcp-server/overview.md > Get median and 95th-percentile agent response latency over time, filtered by date, agent, version, campaign or channel, to spot latency regressions. # Get Latency Trend export const RelatedTopics = ({items}) =>
Related topics
{items.map(([title, href]) => {title} )}
; Plot `bucket` on the X-axis and `p50_ms` and `p95_ms` on the Y-axis. Compare before and after a prompt, model or voice change to catch regressions. ## Notes * `scored` is the number of calls in the bucket with latency data. Buckets with few scored calls are noisy. * Bucket size follows the date range: hour, day, week (labelled with the Monday) or month (labelled with the 1st). Pass `tz` to bucket in your timezone. ## Errors * `400`: a filter is invalid, such as an unknown `channel`, a malformed ID, or `sub_workspace_id` sent from a workspace that isn't a primary workspace. * `401`: `X-API-KEY` is missing or invalid. ## OpenAPI ````yaml get /analytics/v4/latency-trend openapi: 3.0.0 info: title: Ringg AI API Documentation description: >- The Ringg AI REST API. Base URL https://prod-api.ringg.ai/ca/api/v0; send your workspace API key in the X-API-KEY header from server-side code only. Requests and responses are JSON. version: 2.0.0 contact: name: Ringg AI support email: admin@ringg.ai url: https://docs.ringg.ai servers: - url: https://prod-api.ringg.ai/ca/api/v0 security: - ApiKeyAuth: [] tags: - name: workspace description: Endpoints for managing your workspace. - name: agent description: Endpoints for managing agents. - name: calling description: Endpoints for making and managing calls. - name: campaign description: Endpoints for managing campaigns. - name: analytics description: >- Analytics v4 endpoints for call, agent, cohort and chat performance metrics. - name: termination description: Endpoints for terminating active calls using different methods. - name: knowledgebase description: Endpoints for managing knowledge bases. paths: /analytics/v4/latency-trend: get: tags: - analytics summary: Get Latency Trend description: Returns p50 and p95 agent response latency over time. operationId: getLatencyTrend parameters: - name: start_date in: query description: >- Start of the reporting window. Accepts `YYYY-MM-DD` or ISO-8601. Omit both dates for all time. required: false schema: type: string example: '2026-10-01' - name: end_date in: query description: >- End of the reporting window (inclusive). Accepts `YYYY-MM-DD` or ISO-8601. required: false schema: type: string example: '2026-10-15' - name: agent_id in: query description: Filter by one or more agent IDs (comma-separated). required: false schema: type: string example: 00000000-0000-4000-8000-0000000000a1 - name: agent_version_id in: query description: Filter by one or more agent version IDs (comma-separated). required: false schema: type: string example: 00000000-0000-4000-8000-0000000000d1 - name: bulk_list_id in: query description: >- Filter by one or more campaign (bulk list) IDs (comma-separated). Callback calls inherit the campaign of their parent call. required: false schema: type: string example: 00000000-0000-4000-8000-0000000000c1 - name: voicemail in: query description: >- `true` returns only voicemail calls, `false` excludes them. Omit to include all calls. required: false schema: type: boolean example: false - name: channel in: query description: >- Filter by call channel (comma-separated): `inbound`, `outbound`, `webcall`. Unknown values return `400`. required: false schema: type: string example: outbound - name: include_callback in: query description: >- Include callback-feature calls (`call_category = CALLBACK`) in the metrics. Defaults to `false`. required: false schema: type: boolean default: false example: false - name: sub_workspace_id in: query description: >- Primary workspaces only: limit the combined analytics to these Ringg Spaces. Repeat the parameter for multiple IDs. The primary workspace's own ID is accepted; any other workspace sending this parameter gets `400`. required: false schema: type: array items: type: string format: uuid example: - 00000000-0000-4000-8000-000000000101 style: form explode: true - name: tz in: query description: >- IANA timezone used to bucket the time series (for example `Asia/Kolkata`). Bucket labels are returned in this timezone. Omitted or invalid values fall back to UTC. required: false schema: type: string example: Asia/Kolkata responses: '200': description: Latency trend retrieved successfully. content: application/json: schema: type: object properties: by_bucket: type: array items: type: object properties: bucket: type: string description: >- Time bucket label. Granularity is picked from the date range: hour `YYYY-MM-DD HH:00:00`, day `YYYY-MM-DD`, week (Monday) or month (first day). p50_ms: type: number description: Median latency in milliseconds. nullable: true p95_ms: type: number description: 95th-percentile latency in milliseconds. nullable: true scored: type: integer description: Calls in the bucket with a latency measurement. example: by_bucket: - bucket: '2026-10-14' p50_ms: 883.4 p95_ms: 1074.7 scored: 30 - bucket: '2026-10-15' p50_ms: 910.2 p95_ms: 1180 scored: 41 '400': description: >- Bad Request - invalid filter value (for example an unknown `channel` or malformed ID). content: application/json: example: message: 'invalid channel(s): sms' '401': description: Unauthorized - Invalid or missing authentication. '500': description: Internal Server Error. content: application/json: example: message: Failed to fetch latency trend! components: securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-KEY ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.