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

NameTypeRequiredDescription
idstringThe media asset id returned when it was created.

Response

FieldTypeAlwaysDescription
idstringMedia asset id. Use it to attach the asset to a post.
keystringObject key in the product bucket. Private — hand it to no one, it is not a URL.
mimestringStored media type, or null while still pending.
errorstringWhy the asset is failed — a readable reason, or null when nothing went wrong.
sourcestringHow the bytes arrived: url (fetched by the toolkit) or upload (PUT by the app).
statusstringStorage status: pending (the bytes are not in the bucket yet) -> ready (stored, attachable to a post) or failed (ingestion gave up; see error).
filenamestringOriginal filename, kept for display only.
createdAtstringISO-8601 creation time.
sizeBytesintegerStored size in bytes, or null while pending.
sourceUrlstringThe URL the bytes were fetched from, if any.
updatedAtstringISO-8601 time of the last change.

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.

navigateselect