Deprecation Timeline
Find your own legacy calls
Every v1 and v2 response tells you it is legacy and names its replacement, so you can inventory a codebase by running it rather than reading it. Responses carryDeprecation: true and a Sunset header of Sat, 31 Oct 2026 00:00:00 GMT, and the JSON body gains a warning object:
v3_endpoint is the exact operation to move to. Log it across a day of traffic and you have your migration list.
Feature Comparison
On v3, avatar video generation selects a rendering engine per request, Avatar III, IV, or V, through the
engine field. See Models.
v3-Only Features (No Legacy Equivalent)
v3 Platform Improvements
Migration Checklist
- Inventory your v1/v2 calls by logging the
warning.v3_endpointfield on legacy responses - Replace
POST /v2/video/generatewithPOST /v3/videos, including multi-scene calls, which becometype: "studio" - Replace
GET /v1/video_status.getwithGET /v3/videos/{video_id} - Replace
POST /v1/video_agent/generatewithPOST /v3/video-agents - Replace avatar and voice listing calls with
GET /v3/avatarsandGET /v3/voices - Replace
POST /v1/audio/text_to_speechwithPOST /v3/voices/speech - Replace
POST /v2/template/{id}/generatewithPOST /v3/templates/{id} - Replace
POST /v2/video_translatewithPOST /v3/video-translations, and read captions from the detail response instead ofGET /v2/video_translate/caption - Replace
GET /v1/user/meandGET /v2/user/remaining_quotawithGET /v3/users/me - Move
/v1/webhook/endpoint.*management to/v3/webhooks/endpoints - Update pagination logic to cursor-based where applicable
- Test all migrated endpoints in staging before October 31, 2026

