Automotion documentation
Render real MP4 videos from a JSON document — over an API, from templates, or generated by AI.
Automotion turns a JSON document into a rendered MP4. You describe scenes, text, images, video clips, voiceovers and subtitles in the Automotion Movie Schema; the API renders it and hands you back a video URL.
The document is the whole truth: what you send is exactly what renders — no hidden fields, no server-side mutations, and every validation error points at the exact JSON path that caused it.
Start here
| I want to… | Go to |
|---|---|
| Render my first video in 5 minutes | Quickstart |
| Make a faceless short with voiceover + subtitles | Guide: faceless short |
| Render personalized videos from data | Guide: data-driven video |
| Turn a list of images into a slideshow | Guide: slideshow |
| Automate with n8n / Make / Zapier | Automation recipes |
| Look up any schema field | Schema reference |
| Understand auth, limits and errors | API overview |
| Verify webhook signatures | Webhooks |
| Decode an error code | Error catalog |
The 30-second mental model
- Write a movie document — scenes containing elements (
text,image,video,audio,voice,subtitles,component). - POST it to
https://api.automotion.dev/v1/renderswith your API key. - Poll
GET /v1/renders/{id}(or receive a signed webhook) untilstatusisdone, then downloadoutputUrl.
Templates add {{variables}} on top — declare them once, then render the same
template with different values per request. AI generation goes one step
further: describe the video you want and get a schema-valid document back to
edit and render.