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 .md to its URL (for example, /changelog/2026/5/5.md).
  • For the complete documentation index, see /llms.txt.

Video clip reference media and per-team rate limits

This release expands the reference inputs accepted by generate-video-clip and moves rate limiting to a per-team basis. No tools or workflows were removed.

  • Breaking: POST /v1/tools/generate-video-clip replaces the single videoFileId with videoFileIds, an array of up to four reference video file ids. Callers passing videoFileId must rename the field and wrap the value in an array.
  • Reference audio for video clips: generate-video-clip now accepts audioFileIds, up to four uploaded audio file ids used for native lip-sync and soundtrack. As before, at least one of prompt, imageFileIds, videoFileIds, or audioFileIds must be provided, and prompt is optional when any reference media is supplied.
  • Rate limits are now per team: per-endpoint hourly limits are shared across all API keys belonging to your team rather than scoped to a single key. The limit values are unchanged. See Rate limits.
  • Slideshow slideScripts is now index-based: in POST /v1/workflows/add-narration-transitions-and-captions-to-slideshow, each entry maps to the slide at its index, an empty string silences that slide, and fewer entries than slides leaves the remaining slides silent. Pass an empty array ([]) to silence every slide, or omit the field to narrate each slide from its speaker notes. Previously the entry count had to match the slide count exactly or the run failed.
  • Docs: Reworked the introduction’s “What you can build” into separate Workflows and Tools sections, and split the Workflows guide into a section per workflow, each linking to its endpoint reference.