Confirm a completed upload

post

https://api.sintalk.com.br/v3/files/{file_id}/confirm

Step 3 of the three-step direct upload: once the PUT to the presigned URL succeeds, confirm the file so it can be used. status flips from pending to uploaded.

Confirming a file that is already uploaded returns the same result, so a retry is safe. Confirming before the bytes reach storage returns 409 and leaves the file pending, so it can be confirmed again after the upload completes.

Responses

Language

Credentials

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Upload confirmed; the file is uploaded and ready to use.

400The request was rejected before it was applied — either a field failed validation (validation_failed, with error.fields naming each one), or the request could not be read at all (bad_request: malformed JSON, an unknown field, a missing parameter, or an unparseable path or query value).

401No credential was presented, or the one presented was rejected.

403The credential is valid but is not allowed to call this operation.

404No resource with that id exists in your account. An id belonging to another account is reported the same way as one that never existed.

409The request collides with what already exists, or with the resource's current state. Re-read the resource before retrying.

429Rate limit exceeded

defaultAn unexpected error. Safe to retry with backoff; use an idempotency key where the operation accepts one.