Avatar voice not ready: 409 avatar_not_ready, voice_not_ready
A video request can fail with 409 avatar_not_ready because the avatar's voice is not ready. How this differs from a plain not-ready avatar, and the retry hint.
Same code, two messages
Both cases answer 409 with code avatar_not_ready. If the avatar status is anything other than ready, the message is Avatar is not ready for video generation. If the status is voice_not_ready, the message is Avatar voice is not ready for video generation.
| Avatar status | Message | Extra details |
|---|---|---|
| Not ready (for example processing) | Avatar is not ready for video generation. | avatar_id, status |
| voice_not_ready | Avatar voice is not ready for video generation. | avatar_id, status, reason voice_not_ready, next_action try_again_after_avatar_voice_is_ready |
What to do
The face exists but the voice is not usable yet. Do not change your script or tier. Wait, read the avatar, and send the same talking-video request again when status is ready. Avatars can be listed with GET /v1/avatar-1.0/avatars.
curl https://api.sume.com/v1/avatar-1.0/avatars \
-H "Authorization: Bearer $SUME_API_KEY"Guard in your pipeline
- After avatar creation, wait for the creation job to complete before queueing videos.
- Treat avatar_not_ready as retryable with a delay, and read details.reason to pick the message you show users.
- Do not retry in a tight loop; use backoff.
Sources
Related posts
More in Developers
- Pick the best of 4 AI image takes automatically with Pillow
Request n=4 from one Sume image call, score each take by edge contrast with Pillow ImageStat, keep the winner, and see what the four takes cost.
- Black Friday bulk queue: reconcile webhooks received against counts
A bulk queue has no webhook, and canceled runs send none. Count terminal events per item, then compare them with the queue's counts to find what is missing.
- Black Friday code freeze checklist for a Sume Format integration
Before the freeze: key scopes, spend caps, idempotency keys, a webhook test, queue failure handling and the rate-limit budget, all drawn from the Sume docs.
- Black Friday webhooks: staging and production URLs for a Sume Format
Webhook URLs must be public HTTPS and are re-checked at delivery. Use a separate URL per environment and send a test delivery before a bulk queue goes out.
Written by Sume