Introducing the BlitzReels video API

Some video work starts in a dashboard; some starts with inputs in another system. We introduced an API for video and project workflows so developers could connect their own tools and repeat a process without doing every step by hand.

The reason to open this route is that a video is sometimes one step inside a larger job. A team may already have the source material and instructions in its own system, and an API gives that system a defined way to work with BlitzReels projects.

The API came with dedicated documentation and explicit operations that assistants could use, too. The SDK and CLI arrived later; the current docs are the place to check which operations and access options are available for what you want to build.

For developers, this makes it possible to design a process around the video work instead of treating the dashboard as the only entry point. The documented operations also make the boundaries easier to understand: build with the actions the API supports, then use the project and its output in the rest of your process.