Deprecation Timeline
Feature Comparison
On v3, avatar video generation supports per-request rendering-engine selection — Avatar III, IV, or V — via the engine field. See Models.
v3-Only Features (No Legacy Equivalent)
v3 Platform Improvements
Migration Checklist
- Inventory all v1/v2 endpoint calls in your codebase
- Replace
POST /v1/video/generateandPOST /v2/video/generatewithPOST /v3/videos - Replace
GET /v1/video_status.getwithGET /v3/videos/{id} - Replace avatar and voice listing endpoints with v3 equivalents
- Replace
POST /v1/video/uploadwithPOST /v3/assets - Replace
GET /v1/user/mewithGET /v3/users/me - Migrate video translation calls to
/v3/video-translations - Update webhook handling from
callback_urlto managed/v3/webhooks/endpoints - Update pagination logic to cursor-based where applicable
- Template API: now available on v3 — migrate
POST /v2/template/{id}/generatetoPOST /v3/templates/{id} - Studio API: now available on v3 — migrate multi-scene
POST /v2/video/generatecalls toPOST /v3/videoswithtype: "studio" - Test all migrated endpoints in staging before October 31, 2026

