Video Editing API

• What the video editing API covers

  A small surface over REST with API key auth: list your templates and their placeholders, start a render with placeholder values, start a batch render, and poll status until the file is ready. That is the whole surface, so integrations stay small. It is a template-render API by design, honest and predictable, rather than a raw per-frame editing engine.

• Placeholders for text, image, video, and audio

  Mark any layer in a template as a placeholder and it becomes a field in the render payload. Swap a product shot, a headline, a background clip, or a voice over file per render. Everything else in the design stays locked, so every output keeps the same animations, captions, and timing.

• Batch render up to 100 rows

  Send up to 100 rows of data in one batch call and get back a render per row. The same CSV upload works inside the app, so marketers can run a list themselves while your service handles scheduled jobs. Pair it with an automated video editing workflow to keep weekly content moving without manual exports.

• Poll status, download the file

  Every render returns a job id you can poll until it finishes. Jobs run on EchoWave's cloud render farm, the same pipeline behind the editor's export button, so what you previewed is what the API produces. When status reports done, fetch the file and store it wherever your stack needs it.

• An MCP server for AI agents

  The published npm package echowave-mcp exposes the same operations to Claude Desktop, Claude Code, and other MCP clients. An AI video agent can list your templates, fill placeholders, and start renders in conversation, no glue code required. The server authenticates with the same API keys as the REST endpoints.

• Templates designed in a full editor

  Templates come out of EchoWave's editor: a multi-track timeline with keyframe animation, 176 caption presets, 81 text and element animations, and 56 transitions. Designers set the look once and developers never hand-write coordinates. Update the template and future renders pick up the change.

• Cloud rendering, zero infrastructure

  There is no FFmpeg binary to maintain, no render queue to autoscale, and no GPU box to watch. EchoWave's render farm handles the encoding and returns MP4 by default, with WebM, MOV, GIF, and audio formats on paid tiers, up to 4K on Pro, with 8K and 120fps on Business.

• Captions, voice over, and visualizers travel with the template

  Anything you build in the editor ships with the template: captions styled from 176 presets including word-by-word karaoke looks, AI voice over generated from 63 voices, music visualizers in 93 styles. API renders reproduce it exactly as designed. For per-render spoken lines, generate the voice over in the editor and swap it in through an audio placeholder.

1. 1

   Design a template in the editor

   Build the video once: timeline, animations, captions, music. Mark the layers that should change per render as placeholders for text, image, video, or audio. The editor is free to use, and the free plan exports HD renders up to 720p with a small removable EchoWave watermark badge.

2. 2

   Create an API key

   Generate a key from your EchoWave account and send it with each request. Call the list endpoint to confirm your template is available, then fetch its placeholder names so you know exactly what the render payload expects.

3. 3

   POST a render, single or batch

   Send the template id with a value for each placeholder to start one render, or attach up to 100 rows of data for a batch. Each job returns an id immediately while the cloud farm does the work.

4. 4

   Poll status and download

   Check the status endpoint until the render reports done, then download the MP4. On a schedule, the whole loop is a short script. Inside an MCP client, the agent runs it for you.

• Personalized outreach at scale

  Drop each prospect's name, company, and logo into placeholders and render a video per row of your CRM export. A hundred custom videos come out of one batch call.

• Product videos from a catalog

  Map product titles, prices, and photos from your store export onto a template and render the whole range. Rerun the batch whenever the catalog changes.

• Localized campaign variants

  Duplicate a campaign across markets by feeding translated copy into the same template's text placeholders. One design, one integration, every language your team writes.

• Podcast and audiogram clips

  Build an audiogram template with one of 93 visualizer styles, then feed each episode's audio and title through the API. Weekly clips render without anyone opening the editor.

• Agent-driven pipelines

  Wire echowave-mcp into Claude Desktop or Claude Code and let an agent pick the template, fill fields from a brief, and start renders. Status checks happen in the same conversation.

• Listings and real estate videos

  Feed address, price, and photo placeholders straight from your listings feed and render a pan-and-zoom video per property. New listings become videos the moment they land in the data.

Based on each tool's public pages as of July 2026. Plans and limits change, so check current pricing pages before you commit to an integration.