List storage sweep findings
GET /admin/storage/sweeps/{id}/findings
Returns the findings recorded for one storage sweep.
You need system.storage.read or system.admin for the whole install; a permission held only for a team doesn’t count. Without one you get 403, and signed-out callers get 401.
The path id is a sweep-run UUID. The handler doesn’t check that the run exists: a well-formed unknown ID returns 200 with items: [] and total: 0, not the declared 404.
Filter with finding for one exact, case-sensitive finding type, or leave it out for all types; empty or unknown values normally match nothing. Results are newest first by detected_at, then by finding UUID ascending. Resolved and unresolved rows are both included, and there’s no resolved-state filter or resolve action here.
total counts every matching row for the run, ignoring paging. It’s read separately from the page, so new findings or run deletion can make the two disagree, and an offset past the end can return an empty list with a positive total. Use limit and a non-negative offset; changing data can make offset pages skip or repeat rows.
Findings record what a scan observed. Retries can duplicate them, they can outlive the storage bytes they refer to, and they can stay after the problem is fixed. Recheck the bytes and their current references before acting. This endpoint doesn’t look at the backend again.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”UUID of the sweep run whose recorded findings to list. A well-formed ID with no findings returns an empty page, whether or not the run exists.
Query Parameters
Section titled “Query Parameters ”Exact finding type to include: missing_object, orphan_object, checksum_mismatch or size_mismatch. Leave it out for all types; an empty or unknown string normally matches none.
Requested page size, from 1 to 200. Defaults to 50.
Number of matching findings to skip, 0 by default. Use a non-negative value. New findings can shift offset pages.
Responses
Section titled “ Responses ”A page of recorded findings and a separately read count under the same filters. An unknown run ID gets this response too, with an empty list and a zero total.
An offset page of findings and a separately read matching count.
object
Recorded findings ordered by detected_at descending, then UUID ascending. Empty when the requested page has no rows.
One recorded scan observation, not a current integrity verdict or a go-ahead to act. Retries can create several findings for the same pair, and this API doesn’t resolve them automatically.
object
UUID of this finding row.
Observed classification. missing_object: backend bytes weren’t found. orphan_object: no matching variant-registry row was found. checksum_mismatch: an original’s hash differs. size_mismatch: the bytes differ from a positive recorded size. One verification attempt records at most one of these for a pair.
Parent object hash associated with the finding. It identifies the original content, not a derivative checksum or an asset UUID.
Full variant key that was examined, such as original or turntable/0028.png.
Diagnostic details recorded by the scan, such as sizes, backend name or abbreviated hashes. They describe scan-time observations, not a fresh check.
Timestamp assigned when the finding row was inserted. Left out only if no timestamp is available.
Resolution timestamp, if one is stored. The current sweep endpoints neither set it nor filter out resolved rows, so it’s normally left out.
Number of finding rows for the run and filter, ignoring pagination and resolution state. It’s read separately from items. The filtered row count can differ from the run record’s separately checkpointed findings_count.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completedResource not found
object
Human-readable error summary
Example
the request could not be completed