What’s new in the VideoGen API. Each entry below covers a single release window with breaking changes, new endpoints, fixes, and SDK updates.
- Subscribe to releases via the RSS feed.
- For machine-readable history, fetch each entry as Markdown by appending
.mdto its URL (for example, /changelog/2026/5/5.md). - For the complete documentation index, see /llms.txt.
v2.5.0 — Video to video
Restyle an existing video from a text prompt with POST /v1/workflows/video-to-video. Pass an uploaded video or a public link, and the output keeps the original’s length, timing, and cuts. The workflow is available to every account in the SDKs, CLI, MCP, the Zapier, Make, n8n, and Pipedream apps, OpenClaw, and the Python agent framework packages. This release also ends export polling cleanly when a finished export’s file is gone, and checks the full cost of large remix batches before they start.
v2.3.5 — Brand, location, and prop entities
The Entities API has three new entity types. Use LOCATION for a place or set you want to keep consistent across scenes, PROP for a background object that is not something you sell, and BRAND to hold a logo, a style guide image, and a writing style. Keep using PRODUCT for anything you sell or promote.
v2.3.4 — Project list includes every project, and hideFromUi is deprecated
GET /v1/projects now returns every project on the team, including projects created in the dashboard. Projects and files you create through the API always show up in the VideoGen app. includeUiProjects and hideFromUi are deprecated and ignored, so existing requests keep working.
v2.3.3 — Storyboard scenes up to 30 seconds
Storyboard-to-video scenes can now run up to 30 seconds at every quality, up from 20, including scenes with spoken lines.
v2.3.2 — Remix actions run in request order
Remix actions now run one at a time in the order you list them, whether you send them on a workflow start (remixActions) or through POST /v1/projects/{projectId}/remix. Each action applies to the project as the previous action left it.
v2.2.0 — Auto-export after a workflow run
Workflow start requests can now render an MP4 before the run is marked succeeded. Set autoExport: true (REST and SDK default is still false). MCP workflow tools default autoExport to true. Zapier, Make, n8n, and Pipedream always auto-export (the field is not shown) and wait until the MP4 is ready. When auto-export is on, wait until status is succeeded and use downloadUrl. Remix actions on the same start request finish before that export.
v2.1.13 — Simpler Zapier, Make, n8n, and Pipedream apps
The no-code apps now start a VideoGen workflow and wait until the exported MP4 is ready. The only instant trigger is project_export.succeeded. Individual media tools, file upload, project lookup, and other webhook triggers are no longer in those apps. Use the REST API or SDKs for that.
Docs no longer advertise unpublished per-framework agent packages. Give an agent VideoGen with the MCP server, or bind the TypeScript or Python SDK in your framework.
v2.1.15 — Auto-export after a workflow run
Workflow start requests can now render an MP4 before the run is marked succeeded. Set autoExport: true (REST default is still false; MCP and Zapier / Make / n8n / Pipedream default true). When it is on, wait until status is succeeded and use downloadUrl. Remix actions on the same start request finish before that export.
v2.1.14 — Auto duration when generate-video-clip omits durationSeconds
Omitting durationSeconds on POST /v1/tools/generate-video-clip (or passing null) now estimates clip length at generate time so spoken text or the visual beat fits. Previously a missing duration was treated as 6 seconds, which rejected spoken clips longer than 6 seconds. Pass a whole number from 1 to 30 to pin an exact length.
v2.1.11 — Hide workflow projects from Home and Projects
Workflow start requests already accepted hideFromUi to keep generated files off the Media page. The same field now also hides the project from Home and Projects unless the viewer turns on Show hidden projects. Direct project URLs and API get/list still work. Defaults to false.
v2.1.8 — Project export webhooks and catalog voice names
You can subscribe to project export completion instead of polling the export GET. Every voiceId field also accepts a catalog displayName (for example Matilda or Charlie) in addition to a vg_voic_… id from GET /v1/resources/tts-voices. Existing clients that send ids keep working.
v2.1.1 — Download and thumbnail URLs on videogen.io
Signed file download and thumbnail URLs in API responses now use VideoGen hosts. uploadUrl for PUT uploads is unchanged.
v2.1.0 — Catalog entities, spoken clips, slideshow themes, and OpenClaw
Version 2.1 of the TypeScript SDK, Python SDK, CLI, MCP server, and OpenClaw plugin. List VideoGen’s built-in catalog on the Entities API, generate spoken lip-synced clips, theme slideshow-to-video decks, and install the OpenClaw plugin from npm or ClawHub.
v2.0.20 — Slideshow theme optional for uploaded decks
Slideshow-to-video no longer requires a theme when you are converting an uploaded PDF or PowerPoint’s original pages.
v2.0.19 — Slideshow to video requires a theme
Slideshow-to-video now requires a slideshow theme so every generated slide shares one design system.
v2.0.20 — Entity ids on generate-image
POST /v1/tools/generate-image now accepts optional actor, product, and visual-style entity ids. The model uses them as identity/reference the same way in-app image generation does.
v2.0.21 — Spoken dialogue, start frame, and longer clips on generate-video-clip
POST /v1/tools/generate-video-clip now accepts spokenDialogue (the exact line the subject should speak as native, lip-synced speech) and voiceDescription (how that voice should sound). The model synthesizes the voice from that text. audioFileIds still accepts a reference recording for lip-sync from that file. You can pass spoken text, reference audio, or both.
v2.0.22 — Suppress background music on generate-video-clip
POST /v1/tools/generate-video-clip now accepts suppressBackgroundMusic. When true, the generated clip will not include a musical soundtrack. Spoken dialogue and environmental sound are still allowed. Use this when you will add background music separately, for example at the project level.
v2.0.19 — Add zoom remix action
You can now apply a Ken Burns zoom to every still image in a project with a remix action.
v2.0.18 — Actor entities replace avatar presenters
Avatar generation now uses reusable ACTOR entities exclusively.