TEtellers
accepts-api-key

Create Uploads

Start uploading assets.

A single-part asset gets its presigned_put_url. A multipart asset gets its multipart_upload_id, part size and part count but no part URLs: fetch each part's URL from /assets/multipart/part_urls just before sending that part, and a fresh one for a retry. Part URLs are signed with temporary credentials, so one minted long before use can have expired.

post/users/assets/uploads

Request

  • Base URL
    https://api.tellers.ai (the document declares no server; this is the origin it was published from)
  • Auth
    none declared

Headers

x-api-keystring nullable
authorizationstring nullable

Request body

content_lengthinteger required

The content length of the asset in bytes

upload_idstring required
file_type'video' | 'audio' | 'image' | 'text' | 'pdf' | 'lut' | 'font' | 'placeholder' | 'group_clip' | 'master_clip' | 'aaf' | 'proj_original' | 'folder' | 'project' | 'entity' | 'teller_config'
parent_asset_idstring nullable

Optional asset_id of a folder to upload into. When set, the file's inAppPath is treated as relative to this folder and the user must have write access to it.

multipartboolean

If true, returns presigned multipart upload URLs instead of a single PUT URL.

multipart_part_sizeinteger nullable

Optional multipart part size in bytes (min 5 MiB). If omitted, the server picks one from content_length: 16 MiB, growing for very large files. Read the chosen size from multipart_part_size in the response.

Response

Successful Response

upload_idstring required
asset_idstring uuid required
presigned_put_urlstring nullable
presigned_put_urlsstring[]
multipart_upload_idstring nullable
multipart_part_sizeinteger nullable
multipart_part_countinteger nullable

Changes

No recorded changes to this operation across all 2 revisions of this API.