Skip to main content
Every Avatar request needs a ref_image plus exactly one driving input: ref_image and input accept an HTTPS URL, data URI, base64 value, or multipart file upload.

Drive with an audio clip

Pass the driving voice in input. The avatar lip-syncs and moves to the audio, and the audio duration determines the video length.
For a complete create, poll, and download example, follow the quickstart.

Drive with text

Put a Higgs TTS request under input_tts. Choose a reusable voice, or supply TTS voice-cloning inputs. Do not send input in the same request.

Upload local files

Use multipart/form-data to upload a local image and audio clip without base64 encoding. When driving with text, pass input_tts as a JSON-string form field.

Output sizes

Choose the aspect ratio that best matches the reference image so the subject is not cropped.

Input limits

Assets supplied by URL are fetched by the service and are not subject to the inline payload-size limit.

Common request errors

For failed jobs, log the video ID and complete error object so the request can be traced.

Stream generated video

Use the same audio-driven or text-driven body with the streaming endpoint.

Avatar API reference

Look up every request field and additional option.