HeyGen sets October deadline for API v1 and v2 migrations
HeyGen now lists October 31, 2026 as the support deadline for its v1 and v2 APIs, with all traffic expected to move to v3 from November 1 and several newer video, avatar, batch, webhook, and agent features already v3-only.
HeyGen has put a date on its legacy API migration: v1 and v2 endpoints remain operational through October 31, 2026, then move to end of life on November 1. The company now points new integrations to v3, where its newer video-agent, batch, webhook, avatar, translation, and HyperFrames surfaces are concentrated.
For teams that embedded HeyGen into creator workflows, training pipelines, localization systems, or agent-driven video generation, the deadline is the useful part. The old endpoints are not breaking today, but any integration still built around v1 or v2 needs an inventory pass before Q4 pressure arrives.
HeyGen v3 becomes the migration target
HeyGen's changelog says the formal deprecation timeline is now in place for v1 and v2. Its endpoint comparison page is more explicit: the current window runs through October 31, 2026, while November 1 starts the end-of-support phase and all traffic should be routed to v3 by that date.
The developer quick start reinforces that v3 is the default path for new work. It uses https://api.heygen.com with X-Api-Key authentication and leads with POST /v3/video-agents, a prompt-to-video workflow that can script, choose avatar and voice, and render a finished MP4.
This is a platform API change, not a single feature launch. The migration affects code that generates avatar videos, polls render status, uploads assets, lists avatars or voices, manages webhooks, translates videos, or uses template-based production.
Legacy endpoints still have exceptions
The sunset does not mean every v2 capability has a full v3 replacement today. HeyGen's changelog says the Studio API for multi-scene work and Template API will continue to be supported on v2 until a v3 equivalent is available.
That qualifier matters. Teams should avoid treating the migration as a blind endpoint rename. The safer read is: move what v3 already covers, identify the v2-only surfaces that HeyGen explicitly keeps alive, and watch the changelog for the remaining replacements.
HeyGen's comparison page lists direct migration targets for common calls, including replacing POST /v1/video/generate and POST /v2/video/generate with POST /v3/videos, GET /v1/video_status.get with GET /v3/videos/{id}, and POST /v1/video/upload with POST /v3/assets.
What v3 adds for video automation
The v3 surface is broader than the legacy video generator. HeyGen lists v3-only capabilities including lipsync, prompt-based voice design, Starfish text-to-speech, managed webhook endpoints, full Video Agent flows, Avatar Realtime sessions, HyperFrames rendering, background removal, audio search, batch video creation, cursor-based pagination, and unified asset inputs.
Recent changelog entries also show why the migration is becoming more urgent for high-volume users. HeyGen added batch APIs for video translations, lipsyncs, assets, and videos, with up to 100 payloads per call and status endpoints that can check up to 100 IDs. That is a material workflow difference for localization, sales enablement, training, and creator operations that currently loop through single jobs.
What API teams should audit now
Start with a search across code, no-code automations, webhooks, and internal docs for /v1/, /v2/, video_status.get, video_translate, old upload calls, and callback_url-only webhook flows. Then map each call to HeyGen's comparison table and separate clean v3 migrations from v2-only exceptions.
The deadline also affects AI-agent workflows. HeyGen now positions MCP, CLI, and direct API usage as different integration paths, with direct API and Skills using API keys while MCP uses OAuth. If an internal agent generates videos, downloads renders, or manages assets, check which route it uses before the migration window closes.
For LinkLoot readers building repeatable media systems, this belongs next to a broader automation review: keep the production API path current, but also check billing pools, retry behavior, webhook signing, and rate limits. Our AI workflow automation guide is a good place to align those checks with agent-driven content pipelines.
Evidence
The primary evidence is HeyGen's API changelog and endpoint comparison page, which state the October 31, 2026 support window and November 1 end-of-life phase. HeyGen's quick start confirms v3 as the current developer entry point. ME News separately surfaced the v3 quick start and legacy-support deadline, though the operational details should be verified against HeyGen's own docs before changing production integrations.