Skip to content

DocsAPI referenceFiles

Complete a multipart upload

Use multipart.complete_url once every part is received. Answers the completed upload; its input_url then works in jobs. Completing again answers the same. No API key is required.

POST /v1/uploads/{id}/complete

Needs no API key.

Parameters

Parameters
NameInTypeDescription
id requiredpathstring
account requiredquerystring
expires requiredquerystring
signature requiredquerystring

Request

bash
# From the answer of POST /v1/uploads with multipart: true. It needs no API key.
curl --fail-with-body -X POST "https://api.videxo.io/v1/uploads/up_0123456789abcdef01234567/complete?account=acc_7Gq2x9LmTnV4&expires=1793822400&signature=example"

Response

200 JSON
{
  "id": "up_0123456789abcdef01234567",
  "input_url": "videxo://uploads/up_0123456789abcdef01234567",
  "size_bytes": 250000000,
  "sha256": null,
  "content_type": "video/mp4",
  "expires_at": "2026-11-05T12:00:00.000Z"
}

Responses

Responses
StatusBodyWhen
200CompletedUploadThe upload is complete.
401Problemauthentication_failed (client_token_revoked): the client token that created the upload was revoked
403Problempermission_denied (link_invalid, account_disabled)
404Problemnot_found (upload): unknown, deleted or aborted
409Problemconflict (upload_incomplete, upload_used): parts are missing or being sent, or the upload failed
410Problemresource_expired (upload_expired, link_expired)
429Problemrate_limited, with Retry-After in seconds
503Problemservice_unavailable (temporary): the parts are kept; complete again