Sign in

v5

latestOpenAPI 3.1.02026-08-025631,1012.8 MB
Namespace Snapshots

Verify Snapshot Restore-Readiness

Read-only pre-flight check that a snapshot can actually be restored. Restore is lenient and silently skips missing artifacts, so this surfaces what a restore would drop (missing collection dumps, unreachable vectors, absent copied objects) BEFORE you depend on it in a recovery. Pass deep=true to also decompress each collection dump and detect truncation.

get/v1/namespaces/{namespace_identifier}/snapshots/{snapshot_id}/verify

Path parameters

namespace_identifierstring required

Namespace name or ID

Namespace name or ID

snapshot_idstring required

Snapshot ID to verify (e.g. snap_xxxxxxxxxxxx)

Snapshot ID to verify (e.g. snap_xxxxxxxxxxxx)

Query parameters

deepboolean

Also decompress each collection dump to detect truncated artifacts

Also decompress each collection dump to detect truncated artifacts

Response

Successful Response

snapshot_idstring required
statusstring required
restorableboolean required

True iff there are no error-severity issues (a clean restore is possible)

collections_verifiedinteger

Count of expected (non-empty) collection dumps found present

vector_sourcestring nullable

Where vectors would restore from: 'self', the shard-representative prefix (MI-894 coalesced), 'none', or null if unresolved

vector_capturestring

Deep-verify per-point vector NON-emptiness verdict. 'measured_ok': captured points carry non-empty vectors. 'measured_degraded': a significant fraction carry EMPTY vectors — the MI-4393 raw-absence signature (a raw-less point scrolls back with vectors=[] yet counts as captured), so a restore would be searchable-degraded even though the point-count guard passed. 'could_not_measure': not deep-verified, metadata-only, or unreadable. Three-valued by design — could_not_measure must never render as ok (a boolean would collapse incapacity into the healthy value).