Mint signed upload URL

Error

A valid request URL is required to generate request examples

{
  "success": true,
  "data": {
    "uploadUrl": "<string>",
    "token": "<string>",
    "publicUrl": "<string>",
    "blobName": "<string>"
  }
}

POST

uploads

signed-url

Error

A valid request URL is required to generate request examples

{
  "success": true,
  "data": {
    "uploadUrl": "<string>",
    "token": "<string>",
    "publicUrl": "<string>",
    "blobName": "<string>"
  }
}

Mints a short-lived signed upload URL so the file bytes go directly to storage without passing through the API server. Use this for files too large for POST /uploads (or whenever you want to skip the server hop).

The 3-step flow

Mint the URL

POST /uploads/signed-url with a fileName. The response contains uploadUrl and blobName.

PUT the file bytes

PUT the raw file to uploadUrl with the correct Content-Type header.

POST /uploads/complete with the blobName — this verifies the object exists and records it in your media library.

The upload is not in your library until you call /uploads/complete. Unregistered blobs are not listed and cannot be managed via the API.

Example

# 1. Mint
RESPONSE=$(curl -s -X POST "https://mvp2.tryunsora.com/api/v1/uploads/signed-url" \
  -H "Authorization: Bearer uns_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "fileName": "big-video.mp4" }')

UPLOAD_URL=$(echo "$RESPONSE" | jq -r .data.uploadUrl)
BLOB_NAME=$(echo "$RESPONSE" | jq -r .data.blobName)

# 2. PUT the bytes straight to storage
curl -X PUT "$UPLOAD_URL" \
  -H "Content-Type: video/mp4" \
  --data-binary @big-video.mp4

# 3. Register the asset
curl -X POST "https://mvp2.tryunsora.com/api/v1/uploads/complete" \
  -H "Authorization: Bearer uns_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{ \"blobName\": \"$BLOB_NAME\", \"fileName\": \"big-video.mp4\" }"

The Unsora CLI does this automatically: unsora upload ./big-video.mp4.

Authorizations

Authorization

string

header

required

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

Body

application/json

fileName

string

required

Response

200 - application/json

Signed upload URL

success

boolean

data

object

Show child attributes

API documentation

CLI

User

Accounts

Posts

Generation status

Video generator

Image generator

Music generator

Voiceover

AI influencer

Thumbnail generator

Clipping

Uploads

Mint signed upload URL

The 3-step flow

Example

Authorizations

Body

Response

​The 3-step flow

​Example

Authorizations

Body

Response

The 3-step flow

Example