Confirm an uploaded file
Confirm a previously-created file after its bytes have been uploaded to the presigned URL.
The server reads the persisted object back from storage (HeadObject), verifies the size and — when the backend records it — that the SHA-256 matches the checksum supplied at create time, then flips the file from PENDING to CONFIRMED.
When to call: right after the upload PUT returns 200. It is optional but recommended — a file is otherwise confirmed lazily the first time it is fetched via GET /api/v1/files/:id. Idempotent: confirming an already-confirmed file returns its recorded state.
Authorizations
Personal API key, e.g. Authorization: Bearer sajn_sk_.... Not scope-limited — acts as the issuing user.
Headers
Bearer token for API authentication
Makes retries safe. A retry with the same key and the same request replays the stored response for 24 hours (header Idempotent-Replayed: true); the same key with a different request returns 400.
255Path Parameters
Response
File confirmation result
File confirmation result
The confirmed file id
File status after confirmation
CONFIRMED Size in bytes of the persisted object, read back from storage
Whether the storage backend reported a SHA-256 that matched the checksum recorded at create time. False when the backend did not record one (confirmed on size alone).

