For the complete documentation index, see llms.txt. This page is also available as Markdown.

Upload local media

Separate local-file transport from remote media URLs, upload raw bytes, and verify the file before publishing.

Scope: an existing image or video file. This is not the import flow for an n8n workflow template and does not create a generated Visual in the Videos library.

Prompt for your assistant:

Upload this file to Blotato using a presigned upload URL. Send the raw bytes with HTTP PUT, confirm upload success, and use the returned public URL for my post.

  1. Ensure the assistant has access to the file in its workspace.

  2. Call blotato_create_presigned_upload_url with the filename and extension.

  3. Upload the bytes to presignedUrl with an HTTP PUT.

  4. Use publicUrl in blotato_create_post after the upload succeeds.

For REST, create the upload URLs with POST /v2/media/uploads. The upload itself goes to the returned signed URL, rather than to the REST API endpoint.

Request and result

Call blotato_create_presigned_upload_url with this argument, or send it as JSON to POST https://backend.blotato.com/v2/media/uploads with the blotato-api-key header:

{
  "filename": "video.mp4"
}

The response contains presignedUrl and publicUrl. Preserve the returned values. Do not derive one URL from the other or share the signed URL in a support reply.

  1. Send PUT to presignedUrl with the raw file bytes. Do not use JSON or multipart form data.

  2. Check the upload response for success before using publicUrl.

  3. Confirm the file meets the plan and platform limits.

  4. Pass publicUrl in the publish request's mediaUrls array.

  5. Verify the submission's final state separately.

If the client blocks the upload host, resolve the client permission or use a supported environment. If Blotato cannot fetch a remote source, inspect the source host's response instead. These are different request directions. See stage-based diagnosis.

If the file already has a public download URL, pass it directly in mediaUrls. No upload step required. If the assistant lacks file or HTTP access, use a client with those capabilities or provide a public media URL.

See Media uploads and conversion, Upload Media reference, and MCP upload troubleshooting.

Last updated