Skip to content
Plune Plune Plune Docs

Delete a run, and everything it produced

DELETE
/v1/runs/{id}
 
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 30 days 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. The run’s keys go free with it: the same Cairn report sent again, or a start with the same externalKey, makes a new run.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string format: uuid

Responses

Section titled “ Responses ”

204

Section titled “204 ”

Deleted

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

Not found, not yours, or already deleted

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

429

Section titled “429 ”

Rate-limited: the per-route throttle, or the per-minute request limit of the plan an API token counts by (#1442; the body names the plan, #2092). 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