Start a run for a specific test plan.
Documentation Index
Fetch the complete documentation index at: https://api-docs.nunu.ai/llms.txt
Use this file to discover all available pages before exploring further.
project:operate-runstest_plan_id in the body, the plan is identified by the URL path.
The response contains one job_id per test in the plan; poll each one with
Get Job Details to wait for completion.
render_templates is true.options on
Start a Run (min_time_seconds,
max_time_seconds, performance_monitoring, mobile_auto_grant_permissions,
mobile_geolocation, mobile_gpslocation).201 Created on success. The body contains the started-run data
directly (no { ok, status, message, data } envelope) — typically including
job_ids[] (one per test in the plan) and test_plan_execution_id, so the
caller can correlate results via
List Test Plan Executions.
{ "error": "<message>" } with an appropriate HTTP status.
API key for authentication
Test plan ID (UUID)
Run queued
Response body for POST /runs and POST /test-plans/{testPlanId}/runs. Returned with HTTP 201 on success. The body contains the started-run data directly (no { ok, status, message, data } envelope).
Array of job IDs created. Single test returns 1 job; test plan returns one job per test.
Build ID used for the run. Returned for multiplayer test and test plan runs.
UUID of the created ephemeral test. Only returned for ephemeral (instructions) runs.
Test plan execution ID. Returned for test plan runs.
Optional status message returned for multiplayer test and test plan runs.