> ## 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 your workspace's paid concurrency against the concurrency it received over time, hourly for up to two days and daily for longer date ranges. # Get Concurrency Trend export const RelatedTopics = ({items}) =>
Related topics
{items.map(([title, href]) => {title} )}
; Returns the **Concurrency usage** chart in [Analytics](/documentation/monitor/analytics). If `received` keeps reaching `paid`, your calls are waiting on concurrency: raise it on [Billing](/documentation/manage-account/billing#change-concurrency). ## Notes * It covers the whole workspace and takes only the date range, `tz` and `sub_workspace_id`. * `granularity` is `hour` for ranges of two days or less and `day` otherwise. * `available` is `false` when there is no data for the range. ## 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/concurrency-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/concurrency-trend: get: tags: - analytics summary: Get Concurrency Trend description: >- Returns the workspace's paid (guaranteed) concurrency against the concurrency it actually received over time. Buckets are hourly for ranges of two days or less and daily otherwise. operationId: getConcurrencyTrend 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: 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 - 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 responses: '200': description: Concurrency trend retrieved successfully. content: application/json: schema: type: object properties: series: type: array items: type: object properties: bucket: type: string description: >- Bucket label: `YYYY-MM-DD HH:00:00` (hourly) or `YYYY-MM-DD` (daily). paid: type: integer description: Guaranteed concurrency. received: type: integer description: Concurrency the workspace actually received. granularity: type: string enum: - hour - day description: Bucket size. available: type: boolean description: '`false` when there is no data for the range.' example: series: - bucket: '2026-10-15 14:00:00' paid: 5 received: 7 granularity: hour available: true '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 concurrency 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.