HeyGen bulk status for 100 videos at once vs Sume job webhooks

HeyGen's API changelog lists bulk status endpoints that return up to 100 ids per request for videos, lipsyncs, video translations and assets. Sume has no bulk status read for generation jobs in the pages checked here; you poll GET /v1/jobs/{id}/status per job, or let a signed webhook tell you when each one ends.

What HeyGen added

From the HeyGen API changelog, read 2026-10-02:

• The same changelog says batch video creation takes up to 100 videos and returns one batch_id.

How Sume reports status

Every Sume generation returns a durable job. Jobs and results lists the statuses queued, processing, completed, failed and canceled, the last three being terminal, and advises exponential backoff while polling. For avatar video, a queued job is a normal accepted state because workspace concurrency applies when workers pick jobs up.

The alternative to polling is mode: "webhook" with a public HTTPS webhook_url. Webhooks says Sume sends terminal events only: job.completed, job.failed and job.canceled, signed with HMAC SHA 256 over the timestamp and raw body.

A pattern for 100 avatar clips

Submit each clip with its own Idempotency-Key, store the job id in your database, and subscribe by webhook so no loop of 100 reads is needed. Keep a slow poller as a fallback for any delivery that does not arrive.

Do not resubmit a paid request because a local timer expired; read the job first.

• Webhook as the primary signal, polling as the safety net.
• Verify the signature and refuse an empty secret.
• If you want server-side fan-out of many runs, Format bulk runs queue up to 100 runs, but that is a different surface from avatar jobs.