Skip to main content

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 carry Deprecation: 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