Skip to main content
POST
Error
Final step of the signed-URL flow: after PUTting the file bytes to the signed uploadUrl, call this with the blobName from the same response to record the file as an asset in your media library. The server verifies the object actually exists in storage (you get a 400 if the PUT didn’t happen) and reads its size and MIME type from storage metadata. blobName must come from your own signed-URL response — blobs outside your upload prefix are rejected with 403.

Response

Same shape as POST /uploads:

Authorizations

Authorization
string
header
required

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

Body

application/json
blobName
string
required
fileName
string

Response

Registered asset

success
boolean
data
object