Skip to main content

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/generate and POST /v2/video/generate with POST /v3/videos
  • Replace GET /v1/video_status.get with GET /v3/videos/{id}
  • Replace avatar and voice listing endpoints with v3 equivalents
  • Replace POST /v1/video/upload with POST /v3/assets
  • Replace GET /v1/user/me with GET /v3/users/me
  • Migrate video translation calls to /v3/video-translations
  • Update webhook handling from callback_url to managed /v3/webhooks/endpoints
  • Update pagination logic to cursor-based where applicable
  • Template API: now available on v3 — migrate POST /v2/template/{id}/generate to POST /v3/templates/{id}
  • Flag: Studio API (multi-scene) remains v2-only for now; monitor the v3 changelog for a replacement
  • Test all migrated endpoints in staging before October 31, 2026