Skip to content
Plune Plune Docs

What was deleted and can still come back

GET
/v1/bin
 
curl --request GET \
  --url https://beta-api.plune.ai/v1/bin \
  --header 'Authorization: Bearer <token>'

The list behind Settings → Bin, for the caller’s project: suites, test cases and runs that carry deleted_at, newest deletion first, each with the date the purge removes it for good. One entry per deletion — a suite deleted with its subtree is a single entry counting its nodes and cases, and a case that went with it is not repeated below. The way back is the entity’s own restore (POST /v1/suites/{id}/restore, POST /v1/test-cases/{id}/restore, POST /v1/runs/{id}/restore), open to the account owner since D29.

Authorizations

Section titled “Authorizations ”

Responses

Section titled “ Responses ”

200

Section titled “200 ”

The bin, possibly empty in every group

Media type application/json

Everything of the project that lies in the bin, newest deletion first in each group. purgeAt is when the sweep removes it for good — six months after deletedAt, by the database’s own arithmetic.

object
suites
required

One entry per deletion: a node deleted with its subtree counts as one, with nodes and cases saying what went along and comes back with it.

Array<object>
object
id
required
string format: uuid
name
required
string
kind
required
string
Allowed values: folder suite
nodes
required

Child nodes deleted with it

integer
cases
required

Cases deleted with it, from every node of the subtree

integer
deletedAt
required
string format: date-time
purgeAt
required
string format: date-time
testCases
required

Cases deleted on their own. A case that went with its suite is inside the suite’s entry, not here.

Array<object>
object
id
required
string format: uuid
title
required
string
type
required
string
Allowed values: manual automated eval
suite
required

Where it sat; may itself be in the bin now — then its restore answers 409 until the suite is back

object
id
required
string format: uuid
name
required
string
deletedAt
required
string format: date-time
purgeAt
required
string format: date-time
runs
required
Array<object>
object
id
required
string format: uuid
title
required
string
nullable
source
required
string
Allowed values: cli cairn
createdAt
required
string format: date-time
deletedAt
required
string format: date-time
purgeAt
required
string format: date-time
Example 
{
  "suites": [
    {
      "id": "6f1c2b3a-0000-4000-8000-0000000000a1",
      "name": "Checkout",
      "kind": "folder",
      "nodes": 2,
      "cases": 11,
      "deletedAt": "2026-09-16T09:12:04.151Z",
      "purgeAt": "2027-03-16T09:12:04.151Z"
    }
  ],
  "testCases": [
    {
      "id": "6f1c2b3a-0000-4000-8000-0000000000c1",
      "title": "Refund — partial amount @manual @payments",
      "type": "manual",
      "suite": null,
      "deletedAt": "2026-09-16T09:12:04.151Z",
      "purgeAt": "2027-03-16T09:12:04.151Z"
    }
  ],
  "runs": [
    {
      "id": "6f1c2b3a-0000-4000-8000-0000000000d1",
      "title": "plune · 2026-09-16 09:12 · ci",
      "source": "cli",
      "createdAt": "2026-09-16T09:12:04.151Z",
      "deletedAt": "2026-09-16T09:12:04.151Z",
      "purgeAt": "2027-03-16T09:12:04.151Z"
    }
  ]
}

401

Section titled “401 ”

No / invalid token or session