Skip to main content
POST
Create Re-upload Intent

Authorizations

Authorization
string
header
required

API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.

Path Parameters

companyId
string<uuid>
required

Company identifier

fileId
string<uuid>
required

File identifier

Body

application/json
fileName
string
required

File name for the new version (must be non-empty)

contentType
string
required

MIME type of the new version (e.g. application/pdf); must be an allowed type

byteSize
integer
required

Exact size of the new version in bytes (max 1073741824 = 1 GiB)

Response

Re-upload intent created — PUT the bytes to uploadUrl, then finalize

fileId
string<uuid>

Id of the file (unchanged)

versionId
string<uuid>

Id of the new pending version — pass it to finalize

uploadUrl
string

Short-lived signed URL to PUT the new version's bytes to (expires in 15 minutes)