Quickstart
Your first rendered video in five minutes — curl, Node, or Python.
Five minutes from zero to a rendered MP4. You need an API key — create one in
the dashboard (keys are shown once; they look like
am_live_…).
1. Write a movie document
A movie is scenes; scenes are elements. This one is a single 3-second portrait scene with a headline:
Tip: set "draft": true at the top level while iterating — drafts render fast,
low-res and watermarked, and cost half the credits.
2. Create the render
The API answers 201 with the render resource (status: "queued") and a
Location: /v1/renders/{id} header. Send an Idempotency-Key header to make
retries safe — replaying the same key + body returns the original render.
3. Poll until done
Renders move queued → preparing → rendering → done (or failed, always with
a catalog error attached). progress is 0–100 and never goes
backwards. On paid plans you can skip polling entirely by passing a
webhook_url — see Webhooks.
4. Where to next
- Add a voiceover and word-timed subtitles: faceless short guide.
- Reuse one document for many videos: data-driven video guide.
- Every field you can set: schema reference.
- Auth, rate limits, idempotency, pagination: API overview.