Media inputs

Launch generation requests accept media as public HTTPS URLs, in the exact fields that the live OpenAPI schema shows. Before you submit normal Avatar 1.0, Avatar Video, face-swap, or caption requests, you do not need to create a separate Sume asset.

Input URL fields

WorkflowFieldUse for
Avatar 1.0 photo inputinput.image_urlA reference photo for input.type: "photo".
Avatar Video product branchproduct_imageAn optional product/reference image.
Avatar Video scene photo branchscene.image_urlAn optional scene reference when scene.type: "photo".
Avatar Video scene background imagevideo_inputs[].background.urlAn image background for each scene when background.type: "image".
Face swap (Beta)video_urlPublic HTTPS source video for face-swap.
Video captionsvideo_urlPublic HTTPS source video to caption.

Input image/video URLs must be fetchable public HTTPS URLs. Before generation submission, the API rejects localhost, private-network URLs, non-HTTPS URLs, signed/private URLs, and mismatched content types.

Avatar photo example

Use input.type: "photo" with a public HTTPS image_url (edit the fields below if necessary):

Create an Avatar 1.0 identity

POST /v1/avatar-1.0/generate

Required

Avatar Video product example

Create an avatar talking video

POST /v1/avatar-1.0/talking-video

Required

To use the OpenAPI default plus, omit quality.

Face-swap source video example

Create a face-swap job (Beta)

POST /v1/models/sume/avatar-face-swap/v1.0/runs

Required

Generated artifacts

Completed jobs can include artifact objects:

Sume mirrors generated outputs into Sume-owned media URLs before it shows them in public results. Integrations must store the Sume URL, not raw provider URLs. Signed upload/download URLs and private object keys are not part of the launch public API contract.

Trending videos returns public watch URLs for research. In the MVP, it does not mirror downloadable source files.