Run a schedule now (no run ID)

Starts the schedule now, like Run now in the app. The response is 204 No Content and does not include the new test run's ID.

To follow the run you start, for example in a CI pipeline, use POST /v2/schedules/test-runs/{id}/run or POST /v2/schedules/test-runs instead:
both return the new run. The newest run in the list is not always yours,
because other runs can start at the same time.

Requires the TestRun:Create permission.

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

Schedule ID (also called the run-configuration ID), not a scheduler ID.

Headers
uuid

Account UUID. Optional; send it to select the account explicitly.

int64

Organization ID. Optional; send it to select the organization explicitly.

int64
required

Project ID. Required on every request; without it the request returns 400.

Responses
204

The schedule started. No body and no test-run ID.

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Choose an example:
application/json