Skip to content

When the purge last ran, and whether that is recent enough

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

For the schedule to read back after sweeping, not for a screen. stale is true when the last sweep is over 48 hours old OR none has ever run — a deployment that has never purged is exactly the state worth an alarm.

The last sweep

Media type application/json
object
lastPurgeAt
required
string format: date-time
nullable
stale
required
boolean
storageDeletions

The queue of objects to delete from customers’ buckets (#948). Absent only if the count itself could not be read.

object
queued
required

Objects waiting for their deletion.

integer
failing
required

Of those, the ones whose last attempt failed or was refused.

integer
stuck
required

Of those, the ones that have failed for 7 days. They were written to the log once and stay in the queue, retried daily.

integer
oldestAt
required

When the oldest waiting object was queued.

string format: date-time
nullable
byReason
required

Of the failing ones, how many per reason of the last failure: other_bucket, outside_folder, status_<http code> (the bucket answered with it), network, timeout, tls, unresolvable, internal_address, not_https, ip_literal, redirect, error. Only these fixed words, never a key, a link or a bucket name; empty when nothing is failing.

object
key
additional properties
integer
Example generated
{
"lastPurgeAt": "2026-04-15T12:00:00Z",
"stale": true,
"storageDeletions": {
"queued": 1,
"failing": 1,
"stuck": 1,
"oldestAt": "2026-04-15T12:00:00Z",
"byReason": {
"additionalProperty": 1
}
}
}

No / invalid token or session

The caller does not own the application

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