Why a video automation API
Content pipelines rarely live in one app. Ideas come from a spreadsheet, a CMS, a product feed or an AI agent; results need to land in Slack, a CRM or a reporting sheet. A video automation API lets ReelFrames sit in the middle — taking ideas in and sending results out — so video production becomes one step in a larger workflow.
The REST video automation API
Personal API keys
Create a key in Settings → API keys. Keys are scoped to your account and can be revoked at any time. Send them as a Bearer token.
Queue prompts on a campaign
POST to /api/v1/campaigns/{id}/prompts with a list of topics, structured prompts (topic, slide count, style) or CSV. The campaign makes and posts videos from them on its schedule. Requests are rate limited and need a plan with API access.
Video automation API example
A typical call sends {"topics": ["5 morning habits", "Budget meal prep"]} with an Authorization: Bearer header. The response tells you how many prompts were added.
Video automation API with n8n, Make or Zapier
Any tool that can send an HTTP request works: trigger on a new row in a sheet, a new blog post or a new product, and push a topic to the campaign.
Signed webhooks
Each campaign can call your URL when something happens:
- render.completed — a video finished rendering.
- post.published — a post went live on a platform.
- post.failed — a platform rejected a post.
Verifying signatures
Every request carries X-ReelFrames-Event, X-ReelFrames-Delivery, X-ReelFrames-Timestamp and X-ReelFrames-Signature headers. The signature is sha256=HMAC_SHA256(secret, "timestamp.rawBody"). Verify it, reject old timestamps and use the delivery id to de-duplicate — deliveries are at-least-once and retried with backoff.
MCP server for AI agents
ReelFrames runs a Model Context Protocol server at /api/mcp. Connect it to an MCP-capable assistant or agent with an MCP key from the app, and the agent can do what you can do in the app — create slideshows, manage campaigns, schedule posts, check analytics — within the scopes of the key and your role in the workspace.
What you can ask an agent to do
- "Make 5 slideshows about home workouts and schedule them for next week."
- "Which of last week's posts got the most views?"
- "Pause the skincare campaign and copy it for the haircare account."
Keys and permissions
MCP keys work in the workspace you're in when you create them and are limited to what your role allows. Browser cookies never authenticate the MCP endpoint.
Security and fair use
Keep API keys, MCP keys and webhook secrets private and rotate them if they leak. API use counts towards your plan's limits and our terms and acceptable use policy apply.
Video automation API use cases
Teams use the API and webhooks to connect video production to the systems they already run.
Content pipelines built on the video automation API
- Blog to video: when a new article is published, push its title as a topic to a campaign.
- Product feeds: a new product in your store becomes a slideshow prompt.
- Editorial calendars: a row added to a planning sheet queues a video.
- Reporting: post.published webhooks write each post to a spreadsheet or BI tool.
- Alerts: post.failed webhooks ping Slack or email.
AI agents via MCP
Instead of wiring each step yourself, connect an AI assistant to the MCP server and describe what you want in plain language. The agent calls ReelFrames tools to make, schedule and review content.
Video automation API vs MCP: which to use
Use the REST API and webhooks for fixed, repeatable pipelines. Use MCP when you want an assistant to make decisions — choosing topics, reviewing analytics, adjusting campaigns.
Getting started with the video automation API
You can go from zero to a working integration in a few minutes.
Video automation API quick start
- Create a Slide Maker campaign in the app with your accounts, posting times and look.
- Create a personal API key in Settings → API keys.
- Send a test request adding one topic to the campaign.
- Add a webhook URL to the campaign and subscribe to the events you need.
- Verify signatures in your endpoint and store delivery ids to de-duplicate.
Error handling
Expect rate limits and plan checks: if a request is rejected, read the error message, back off and retry. Webhook deliveries are retried automatically with backoff.
Video automation API security checklist
- Store keys in a secret manager, never in client-side code.
- Rotate keys if a teammate leaves.
- Reject webhook requests with old timestamps or bad signatures.