Skip to main content

​
Supported avatar types

digital_twin, studio_avatar, and photo_avatar looks that list avatar_v in supported_api_engines.

​
Supported parameters

  • motion_prompt — natural-language control of body motion and hand gestures.
  • engine.reference_look_id (optional) — a digital_twin look to use as the animation reference. Must belong to the same avatar group as avatar_id, and a non-public one must clear its group’s consent requirements. When omitted, a digital twin or studio avatar references itself, and a photo avatar uses an eligible look from its group. A photo avatar with no eligible look renders directly from its image, and motion_prompt is then rejected.
  • engine.more_blinking (optional): set to true for more natural blinking. Defaults to false.
For expressiveness control, use Avatar IV.

​
Checking eligibility

Avatar V is opt-in per look. Fetch the look with GET /v3/avatars/looks/{look_id}: Avatar V is available when "avatar_v" appears in its supported_api_engines.

​
Example request

Select Avatar V by passing "engine": { "type": "avatar_v" } in your POST /v3/videos request:
Video generation is asynchronous — the response returns a video_id you poll with GET /v3/videos/{video_id}. See the Digital Twin guide for the end-to-end request and polling flow, Models for an engine comparison, or Avatar IV for the default engine.