---
title: "Delete Dedicated Run"
method: DELETE
path: "/api/v1/training/runs/{run_id}"
tags: ["training"]
---

# Delete Dedicated Run

`DELETE /api/v1/training/runs/{run_id}`

Delete a dedicated run: helm uninstall + namespace delete + DB cleanup.

Idempotent. Safe to call repeatedly. Cleans up the linked Job row too
(which uninstalls the helm release on the customer cluster). Soft-
deletes the RFTRun row (matches the existing run-delete UX - Billing
refs are preserved). Access is per-row: `verify_run_ownership`
accepts personal runs the caller owns and team runs the caller is
a member of.

## Path parameters

- `run_id` string, required

## Response `200`

Successful Response

- DeleteRunResponse
  - `runId` string, required
  - `deleted` boolean, required

## Other responses

- `401` — Authorization failed
- `422` — Invalid request data

---

[API](https://skmtc.net/primeintellect/apis/pi-api.md) · [All operations](https://skmtc.net/primeintellect/apis/pi-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/primeintellect/pi-api/versions/60efc9b3ff2a/schema)