Asset id or public HTTPS URL? What Sume inputs accept

Pass a public HTTPS URL in the request field; you do not need to create an asset first. Sume's docs say launch generation requests accept media as public HTTPS URLs and that normal Avatar, face-swap and caption requests need no separate asset. Use an asset id only when your workflow needs the first-party asset lifecycle.

Everything here is from Media inputs and Jobs and media inputs, read 2026-09-30.

Which fields take a URL?

The exact fields are in the live OpenAPI schema; these are the ones the docs list.

Which URLs get rejected?

Localhost, private-network, non-HTTPS and signed or private URLs, and any whose content type does not match, are rejected before generation submission. The troubleshooting page adds a common cause: a URL that needs cookies or a short-lived signature that expires before Sume can fetch it. Related errors are image_not_fetchable and input_media_unreachable; check the URL is public HTTPS, then retry or contact support with the request id.

When is an asset id worth it?

When you want Sume-registered inputs you can list, get and download later. sume assets create --source-url <url> --confirm-submit registers from a public URL; the upload route is covered in the assets flow post. Both are write-gated.

What comes back as output?

Completed jobs list artifacts with an artf_ id, a media.sume.com URL, a type and a content type. Store the Sume URL, not raw provider URLs.