Skip to content
Plune Plune Docs

Put a deleted test case back

POST
/v1/test-cases/{id}/restore
 
curl --request POST \
  --url https://beta-api.plune.ai/v1/test-cases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/restore \
  --header 'Authorization: Bearer <token>'

The reverse of DELETE /v1/test-cases/{id} — for the account that owns the case (Settings → Bin) and for the owner of the deployment; everyone else gets 404, the same 404 an unknown id gets. A case that went with its suite comes back with the suite (POST /v1/suites/{id}/restore), not on its own: asking for it alone answers 409 and names the suite.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

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

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Restored

Media type application/json
object
id
required
string
restored
required
boolean
Example generated
{
  "id": "example",
  "restored": true
}

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

No such deleted case in the caller’s project (the deployment owner reaches every project)

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

409

Section titled “409 ”

The case belongs to a deleted suite — restore the suite instead

Media type application/json
object
error
required
string
code
required
string
Allowed values: suite_deleted
Example 
{
  "code": "suite_deleted"
}

429

Section titled “429 ”

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