seedanceapi
Avatar V · Digital Twin render example

HeyGen · Avatar V · digital human

Avatar V · Digital Twin

Render Avatar V through the same job workflow as Seedance — from $0.162 per render.

Model idheygen/avatar-v/digital-twinShot spec720p · 1080p · 4kRatefrom $0.162

What it renders

HeyGen Avatar V Digital Twin is a fast AI avatar video generation model that creates natural digital twin videos from text or audio with lip-sync, optional captions, background removal, and… Hand over the model id and your shot settings, keep the job id, and collect the finished clip once the job lands. Pricing is per completed render from $0.162 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Avatar V · Digital Twin opens on workable shot framing before you tune anything.

  2. Async by design

    Renders run as background jobs; poll at your own pace instead of holding a connection open.

  3. Clip-ready output

    Results arrive as a downloadable asset from private storage with a short-lived link.

  4. Digital Human shots

    Digital Human stays available for Avatar V · Digital Twin without leaving the video workspace.

  5. Avatar V shots

    Avatar V stays available for Avatar V · Digital Twin without leaving the video workspace.

  6. Video shots

    Video stays available for Avatar V · Digital Twin without leaving the video workspace.

From the shot board

Avatar V · Digital Twin example output.
Avatar V · Digital Twin output
Avatar V · Digital Twin example reference.
Avatar V · Digital Twin reference

Wire the render pipeline

  1. Grab a key

    Sign in, create a server-side key and add a little balance.

  2. Confirm the endpoint

    GET /v1/models lists heygen/avatar-v/digital-twin with its shot limits and current rate.

  3. Queue the render

    POST /v1/jobs with the model id, your shot settings and a unique Idempotency-Key.

  4. Collect the clip

    Poll GET /v1/jobs/{id} until it lands, then fetch GET /v1/jobs/{id}/content.

Queue the render

# Seedance API — queue one render
curl https://seedanceapi.pro/v1/jobs \
  -H "Authorization: Bearer $SEEDANCE_API_KEY" \
  -H "Idempotency-Key: $REQUEST_ID" \
  -H "Content-Type: application/json" \
  -d '{"model":"heygen/avatar-v/digital-twin","aspect_ratio":"16:9","avatar":"Abigail Sofa Front","fit":"cover","output_format":"mp4","remove_background":false,"resolution":"720p","prompt":"A slow dolly across a rain-lit neon street, shallow depth of field."}'

Shot settings

aspect_ratiooptional
string · 16:9 / 9:16
audioneeded
string
avatarneeded
string · default Abigail Sofa Front
fitoptional
string · cover / contain
output_formatoptional
string · mp4 / webm
remove_backgroundoptional
boolean · default false
resolutionoptional
string · 720p / 1080p / 4k

Try a render from here

This queues a real job on this site's /v1/jobs using your signed-in balance, or an API key if you are not signed in. A pasted key lives only in this tab; the render is billed at the quoted USD rate.

Or sign in to use your account balance.

Before you wire it in

How do I start a Avatar V · Digital Twin render?

Authenticate, check the live model list for heygen/avatar-v/digital-twin, then POST the model id and shot settings to /v1/jobs with an Idempotency-Key. Poll the job id until it settles, then download the clip.

What can I control on Avatar V · Digital Twin?

Avatar V · Digital Twin accepts aspect_ratio, audio, avatar, fit, output_format, remove_background, resolution. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Avatar V · Digital Twin render cost?

Pricing is per render and starts at $0.162. The exact figure for your settings is returned by the model list and reserved before the job is accepted.

Is the same Seedance key valid for Avatar V · Digital Twin?

Yes — Avatar V · Digital Twin runs on the same account, key and wallet as Seedance. Each endpoint is enabled individually, so verify the route before you depend on it.

Why does my Avatar V · Digital Twin job show as queued?

Video rendering is asynchronous: queued and running are normal. Keep polling until the job succeeds, fails or asks for review, and never resubmit the same Idempotency-Key expecting a second render.

More endpoints like this