Skip to content

content_media_finalize

Confirm a signed-URL upload.

Tool

content_media_finalize

Confirm a signed-URL upload.

Confirm a signed-URL upload. The bucket is asked what was actually stored, and the asset becomes ready. Fails while no object has been uploaded yet.

Behavior

HTTP
POST /content/media/:id/finalize

Arguments

Name
Type
Required
Description
id
string
•
The media asset id returned when it was created.

Response

Field
Type
Always
Description
id
string
•
Media asset id. Use it to attach the asset to a post.
key
string
•
Object key in the product bucket. Private — hand it to no one, it is not a URL.
mime
string
•
Stored media type, or null while still pending.
error
string
•
Why the asset is failed — a readable reason, or null when nothing went wrong.
source
string
•
How the bytes arrived: url (fetched by the toolkit) or upload (PUT by the app).
status
string
•
Storage status: pending (the bytes are not in the bucket yet) -> ready (stored, attachable to a post) or failed (ingestion gave up; see error).
viewUrl
string
•
One-hour signed GET URL for a ready asset, or null while pending or failed. Treat it as a bearer link.
filename
string
•
Original filename, kept for display only.
createdAt
string
•
ISO-8601 creation time.
sizeBytes
integer
•
Stored size in bytes, or null while pending.
sourceUrl
string
•
The URL the bytes were fetched from, if any.
updatedAt
string
•
ISO-8601 time of the last change.
viewUrlExpiresAt
string
•
ISO-8601 expiry of the signed view URL, or null when no view URL is available.

Try it

Confirm a signed-URL upload.

When to use

Confirm a signed-URL upload. The bucket is asked what was actually stored, and the asset becomes ready. Fails while no object has been uploaded yet.

Example

Ask your agent something like this:

Confirm a signed-URL upload.

The agent will invoke content_media_finalize with these arguments:

{
  "id": "<id>"
}

Esc

Start typing to search the docs.

↑↓navigate↵select