---
title: "Series beta: recurring videos through the API and CLI"
canonical: "https://blitzreels.com/changelog/introducing-series-beta"
---

# Series beta: recurring videos through the API and CLI

Milestone: 2026-09-10
Article published: 2026-09-26
Status: Beta

Group recurring videos around a shared identity through the API and CLI. Series is an optional beta for Growth and above.

![Three miniature episodes grouped around one shared visual identity.](https://blitzreels.com/images/changelog/introducing-series-beta.jpg)

## For the idea you want to come back to

Some video ideas deserve another episode. Series lets you group existing videos around a shared identity through the API and CLI, without duplicating the content to get started.

Returning to a format means keeping track of more than the last finished file: the related videos and their creative defaults belong together. We worked on Series to give that recurring part of production a place in your video workflow, with the next piece alongside what came before it.

## Organize the series from your own tools

The public API and CLI let you list a series, inspect its identity and defaults, and assign existing sources or projects to it. You can also update those defaults as the format develops, while keeping the content connected to the same series.

For a developer building a recurring video workflow, this gives the shared part of the process a place to live. Your code can work with the series identity alongside the individual videos, instead of treating every new piece as an unrelated project.

## An optional beta for Growth and above

Series is available through the API and CLI on Growth and higher plans, with workspace permissions still applying. This story covers those developer tools; start with the CLI guide to explore the available commands.

## Give an ongoing idea a place in your workflow

Use the CLI guide to get started, then explore the Series commands with your workspace on Growth or above.

[Read the CLI guide](https://blitzreels.com/docs/cli)

We wrote this story later, looking back at our product history. The date at the top marks the work described here; features and access may have changed since then.