Archive or permanently delete a Solution run

DELETE

/api/solutions/runs/{run_id}/

const url = 'http://localhost:8000/api/solutions/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 http://localhost:8000/api/solutions/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/ \
  --header 'Authorization: Bearer <token>'

Two-step trash (#1192): a plain DELETE soft-archives the run (it drops out of the active list but stays recoverable and its share links keep resolving). ?permanent=true hard-deletes an archived run — its share links CASCADE with it and it can’t be recovered. Team-scoped; cross-team is a 404.

Authorizations

Parameters

Path Parameters

run_id

required

string format: uuid

Query Parameters

permanent

boolean

true hard-deletes (irreversible) instead of soft-archiving.

Responses

204

Archived or deleted.

404

application/json

object

detail

required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string

Example^generated

{
  "detail": "example"
}