Confirm an Upload

Mark a file as status='uploaded' once the browser’s S3 PUT succeeded.

Verifies via S3 HEAD that the object actually exists; if not, returns 409 so the frontend can retry. Idempotent — re-confirming an already-uploaded file just re-verifies and returns the row.

POST /files/{file_id}/confirm-upload

Confirm Upload

cURL

curl --request POST \
  --url https://api.example.com/files/{file_id}/confirm-upload \
  --header 'Authorization: Bearer <token>'

200

{}

Step 2 of the upload flow (see Initiate an Upload). Verifies via an S3 HEAD that the object actually landed, then sets status: "uploaded". Idempotent — calling it again on an already-uploaded file just re-verifies and returns the row unchanged.

Auth

Requires a CRM manage scope and an active organization on the token. Any *:manage scope qualifies — in practice contacts:manage, deals:manage, companies:manage, or activities:manage.

Response

Returns the updated files row (same shape as file in Initiate an Upload), with status: "uploaded".

Errors

Status	Cause
404 Not Found	File doesn’t exist (or isn’t in this org, or is archived).
409 Conflict	The object isn’t visible in S3 yet — retry shortly.
502 Bad Gateway	The S3 HEAD call itself failed.

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

file_id · string · required

UUID of the file to confirm as uploaded.

Response

200

application/json

Successful Response

The response is of type Response Confirm Upload Files File Id Confirm Upload Post · object.