Query test run counts

Retrieve the count of test runs in an active workspace, aggregated into time buckets. Each bucket reports the total number of runs that started within the bucket window, as well as how many of those passed and how many failed or were terminated. Useful for plotting test activity over time, tracking reliability trends, and feeding external dashboards with per-day/week/month usage metrics.

Runs are counted by their start_time, not end_time — a long-running test that starts on day D and finishes on day D+1 is attributed to day D. In-flight runs (ones that have started but not yet completed) are included in total_test_runs and counted as failed_test_runs until they complete, since they have not yet succeeded.

Optional filters (application_id, plan_id, test_type) narrow the underlying row set. Optional group_by (plan or application) breaks each time bucket further into one bucket per group value, with the group_id field on each bucket identifying the dimension value.

All timestamps in requests and responses are Unix epoch milliseconds. Bucket boundaries are aligned to UTC; convert to local time on the client side if needed. Time range is capped by granularity: daily (90 days), weekly/monthly (400 days). Data is served live from the test run database, so results reflect runs completed within seconds of the request.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The workspace ID

Query Params
int64
required

Inclusive start of the time range to report on, as Unix epoch milliseconds. Must be strictly less than end_time.

int64
required

Exclusive end of the time range to report on, as Unix epoch milliseconds. Must be strictly greater than start_time. The total window end_time - start_time is capped by granularity: 90 days for daily, 400 days for weekly or monthly. Requests exceeding the cap return HTTP 400.

string
enum
required

Time bucket size for the response. Valid values are daily, weekly, and monthly. Daily buckets start at midnight UTC. Weekly buckets follow ISO-8601 week boundaries (Monday 00:00 UTC). Monthly buckets align with the first day of each calendar month at 00:00 UTC.

Allowed:
string
enum

Optional dimension to break the response down by. Without group_by, each time bucket aggregates all matching runs. With group_by set, each time bucket is further split by the grouping value and the group_id field on each bucket identifies which plan, application, or workspace it represents (workspace only appears on account-level endpoints). Buckets are emitted for every (period, group_id) combination that has at least one matching run; combinations with zero runs are omitted.

Allowed:
string

Filter results to runs associated with a specific mabl application. Only runs whose application_id matches this value exactly are included. Combined additively with other filters (plan_id, test_type) — runs must match all provided filters.

string

Filter results to runs that were part of executions of a specific test plan. Useful for attributing usage to a particular CI pipeline, schedule, or deployment trigger. Runs not associated with any plan (for example, ad-hoc runs from the Trainer) are excluded when this filter is set.

string
enum

Filter results to runs of a specific test type. Valid values are browser (UI automation), api (REST API tests), mobile, and performance. Useful when a workspace exercises multiple test types and you want to report on them independently — for example, to split UI-automation usage from API-test usage in an attribution dashboard. When omitted, all test types are included.

Allowed:
Responses

Language
Credentials
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json