Skip to content
Plune Plune Docs

File every automated case that has no suite, in every project, by its specRef

POST
/v1/admin/file-unfiled
 
curl --request POST \
  --url https://beta-api.plune.ai/v1/admin/file-unfiled \
  --header 'Authorization: Bearer <token>'

A deployment-level operation like the purge, run once after the wave-1 deploy of B-7 (AC-17). Walks every project — each in its own transaction — and files every automated case without a suite through the same seam a freshly created case goes through: folders and suites are found or created, the case gets its suiteId, and the derived nodes and the case are audited under the caller. A case whose path meets a node of the same name but the other kind stays in the root and is reported under skipped with the reason (AC-14). Idempotent: a second run reports filed: 0 everywhere and the same skipped. Restricted to the owner of the deployment; everyone else gets 404 — the route does not exist for them.

Authorizations

Section titled “Authorizations ”

Responses

Section titled “ Responses ”

200

Section titled “200 ”

What was filed and what was skipped, per project

Media type application/json

What the sweep filed and what it skipped, per project.

object
projects
required
Array<object>
object
projectId
required
string
filed
required

Cases that got a suiteId in this run.

integer
skipped
required

Cases left in the root because their path meets a node of the other kind (AC-14).

Array<object>
object
caseId
required
string
reason
required
string
Example 
{
  "projects": [
    {
      "projectId": "userA::default",
      "filed": 2027,
      "skipped": [
        {
          "caseId": "6f1c2b3a-0000-4000-8000-0000000000c3",
          "reason": "filing skipped: 'e2e' exists as a suite, expected a folder"
        }
      ]
    },
    {
      "projectId": "userB::default",
      "filed": 0,
      "skipped": []
    }
  ]
}

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

The caller does not own the application

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

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