Delete a run, and everything it produced
DELETE
/v1/runs/{id}
const url = 'https://beta-api.plune.ai/v1/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://beta-api.plune.ai/v1/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>'Soft. The run and the review-queue entries it produced stop being readable at once; the rows are purged for good six months later. Results are not listed separately because they are only ever read through their run. Deleting is the account owner’s own business and takes no confirmation; putting it back is not theirs to do — see POST /v1/runs/{id}/restore. A second DELETE answers 404 rather than 204, so a typo in the id cannot read as a success.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ” id
required
string format: uuid
Responses
Section titled “ Responses ”Deleted
No / invalid token or session
Not found, not yours, or already deleted
Media type application/json
object
error
required
string
Example generated
{ "error": "example"}Rate-limited: either the per-route throttle or a tenant quota. Retry-After carries the seconds until the window rolls over.
Media type application/json
object
error
required
string
Example generated
{ "error": "example"}Headers
Section titled “Headers ” Retry-After
integer
Seconds until the window rolls over