Start Test Plan Run
Start a run for a specific test plan.
project:operate-runstest_plan_id in the body, the plan is identified by the URL path. It is also
the only endpoint that accepts slot_deployment_configs for cross-platform
plans.
The response contains one job_id per test in the plan; poll each one with
Get Job Details to wait for completion.
Path Parameters
Request Body
slot_deployment_configs is supplied.deployment_config_id; otherwise the
request returns a 400 error."2", "3", and so on). Fetch the plan with
Get Test Plan to see its slots.
Every slot used by the plan’s player assignments needs an entry; keys
referencing slots the plan does not define return a 400 error. The key
"1" addresses the default slot as an alternative to the top-level
deployment_config_id/build_id (supplying both returns a 400 error).
Private device configs are allowed, but every player on a private device
needs its own device; if the configs of a test cannot give each of its
players a distinct device, the request returns a 400 error.render_templates is true.options on
Start a Run (performance_monitoring,
mobile_auto_grant_permissions, mobile_geolocation, mobile_gpslocation).
Time-budget overrides are intentionally not accepted here; the budget
lives on the test version itself (min_seconds / max_seconds).Response
Returns201 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.
Authorizations
API key for authentication
Path Parameters
Test plan ID (UUID)
The project ID. You can copy it from the project settings page or the project URL in the dashboard.
Body
- Option 1
- Option 2
UUID of the deployment config for the plan's default slot (slot 1), used by every player not assigned to an extra slot. Required unless the plan's slot assignments cover every player and slot_deployment_configs is supplied.
UUID of a build from Build Storage for the default slot. Only works with build-storage deployment configs, and requires deployment_config_id.
Per-slot deployment configs for cross-platform test plans, keyed by slot index ("2", "3", and so on; see the plan's slots). The key "1" addresses the default slot and cannot be combined with deployment_config_id/build_id. Every slot used by the plan's player assignments needs an entry. Private device configs are allowed, but every player on a private device needs its own device; if the configs of a test cannot give each of its players a distinct device, the request returns a 400 error.
Per-run override knobs. The time budget is intentionally not overridable here; it lives on the test version itself (see min_seconds / max_seconds on the test body), so callers should edit the test (or create a new version) when they want to change the budget.
Response
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.
For cross-platform test plan runs: the build pinned for each extra slot, keyed by slot index. Only present when slot configs resolved to builds.
Optional status message returned for multiplayer test and test plan runs.