Confirm an uploaded file
2026-09, which is deprecated and stops working on October 1, 2027. To move your integration, see Upgrading to 2026-10.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.
AuthorizationBearer <token>Personal API key, e.g. Authorization: Bearer sajn_sk_.... Not scope-limited — acts as the issuing user.
id*stringIdempotency-Key?stringMakes 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.
length <= 255File confirmation result
application/json- response
File confirmation result
id*stringThe confirmed file id
status*"CONFIRMED"File status after confirmation
"CONFIRMED"size*numberSize in bytes of the persisted object, read back from storage
checksumVerified*booleanWhether 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).
curl -X POST 'https://app.sajn.se/api/v1/files/string/confirm' \ -H 'authorization: string'{ "id": "string", "status": "CONFIRMED", "size": 0, "checksumVerified": true}Was this page helpful?