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 it unchanged.
Response: Returns the file in the shape of GET /api/v1/files/:id.
Authorizations
Personal API key, e.g. Authorization: Bearer sajn_sk_.... Not scope-limited — acts as the issuing user.
Headers
API version for this request. Without it, the request uses the organization's default version; an organization without a default is pinned to the latest version by its first request.
2026-09, 2026-10 ID of the workspace this request acts in, from GET /api/v1/workspaces. Without it, an API key acts in its default workspace. The token's user must be a member of the workspace; an OAuth token only accepts the workspace it was granted for. A workspace that doesn't exist or can't be reached returns 403 WORKSPACE_ACCESS_DENIED.
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
The file ID.
Response
File information with access URL
File information with access URL
Unique file identifier
Original filename
MIME type of the file
File size in bytes
File visibility
PRIVATE, PUBLIC URL to access the file (signed URL for private, direct URL for public)
Date and time when file was uploaded
Date and time when file was last updated
The user who uploaded the file

