Delete Run — DELETE /api/v1/runs/{run_id}
Delete Run
Delete one run across all five stores. Irreversible.
Endpoint: DELETE /api/v1/runs/{run_id}
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- Your role must be Admin or higher.
- You must have access to this test run.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
run_id | path | yes | string (uuid) | ||
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”| Content type | Body | Required |
|---|---|---|
application/json | DeleteRunRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
202 | Successful Response | DeleteRunAcceptedResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
404, with the message “Test run not found”409, with the message “Run is still executing. Deleting it now races the drainer and the persist task, which would re-create the row with none of its data. Stop the run first”422, with the message “confirm must be true — this deletes across five stores and cannot be undone”
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Test Runs
- Operation ID:
delete_run_api_v1_runs__run_id__delete - Source code:
backend/app/routers/runs.py, line 965 - Specification: OpenAPI JSON