d0fc0114da66
Query workspace daily maximum concurrent test runs
Retrieve the daily maximum number of simultaneously executing test runs in an active workspace, along with the workspace's configured test run concurrency limit for the same test type. The reported max_test_run_concurrency is computed as the maximum number of runs executing at any single instant during the day — not an average, not a count of runs started. If ten runs start and finish within the same minute but a different run was also executing for that minute, the maximum for that minute is eleven.
Use this endpoint to track how close a workspace is running to its purchased concurrency capacity, decide when to request a limit increase, identify load bursts, or correlate peak usage with customer-side deployment or traffic patterns. Compare the max_test_run_concurrency values against configured_test_run_concurrency_limit to see headroom.
Data is pre-aggregated from billable events by a background job that runs every 12 hours, so values for the current calendar day may be incomplete until the next aggregation cycle finishes. Time range cannot exceed 90 days. If start_time and end_time are both omitted, the endpoint returns the last 90 completed days ending at the start of the current UTC day.
The configured_test_run_concurrency_limit is resolved against the requested test_type. For browser (the default when unspecified), it is the sum of the workspace's Linux, macOS, and Windows browser quotas. For api, mobile, or performance, it is the single numeric quota for that resource. A workspace with no configured quota for a given test type returns configured_test_run_concurrency_limit: 0.
Path parameters
The workspace ID
Query parameters
Inclusive start of the time range to report on, as Unix epoch milliseconds. Must be earlier than end_time. Optional: if both start_time and end_time are omitted, the endpoint returns the most recent 90 completed days. If end_time is provided but start_time is not, start_time defaults to 90 days before end_time. Any sub-day precision is snapped to midnight UTC of that day; the response echoes the snapped value.
Exclusive end of the time range to report on, as Unix epoch milliseconds. Must be later than start_time. Optional: defaults to the start of the current calendar day in UTC (i.e. the end of the most recent completed day). The window end_time - start_time cannot exceed 90 days. Any sub-day precision is snapped to the start of the following UTC day; the response echoes the snapped value.
Test type to report maximum test run concurrency for. Valid values are browser (UI automation), api (REST API tests), mobile, and performance. The returned max_test_run_concurrency values and the matching configured_test_run_concurrency_limit both reflect the selected test type. Defaults to browser when omitted.
Response
Daily maximum concurrent test run data for the workspace