Skip to main content
GET
Get Concurrency Trend
Returns the Concurrency usage chart in Analytics. If received keeps reaching paid, your calls are waiting on concurrency: raise it on Billing.

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.

Authorizations

X-API-KEY
string
header
required

Query Parameters

start_date
string

Start of the reporting window. Accepts YYYY-MM-DD or ISO-8601. Omit both dates for all time.

Example:

"2026-10-01"

end_date
string

End of the reporting window (inclusive). Accepts YYYY-MM-DD or ISO-8601.

Example:

"2026-10-15"

tz
string

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.

Example:

"Asia/Kolkata"

sub_workspace_id
string<uuid>[]

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.

Example:

Response

Concurrency trend retrieved successfully.

series
object[]
granularity
enum<string>

Bucket size.

Available options:
hour,
day
available
boolean

false when there is no data for the range.