API reference · Platform

Films

Saved storyboard drafts: a shared look plus ordered scenes.

GET/v1/filmsFree

A film is a RECIPE, never media: a title, a shared look (film type, era, tempo, camera, format) and ordered scenes (prompt, camera move, duration, cast). Up to 50 drafts per account; the studio's Film mode saves and reloads them here. Renders always land in /v1/creations.

POST /v1/films creates one (title, data); GET /v1/films/{id} returns the full recipe; PATCH /v1/films/{id} updates title and/or data; DELETE /v1/films/{id} removes the draft (its renders stay in the library). data is yours — the API stores it verbatim.

POST /v1/films/{id}/render shoots the whole storyboard in one call: every scene with a prompt is queued as an async video job (charged per scene, like POST /v1/videos/generations), the response maps each scene to its job id (poll them) or to the error that kept it from queueing. Scenes fail independently — a drained wallet stops the remaining queue cleanly, and every charged failure refunds itself.

curl https://eroq.ai/v1/films \
  -H "Authorization: Bearer $EROQ_API_KEY"

/v1/filmsno network

→ GET /v1/films

Press run — this replays a real exchange from the docs' own data. No key, no request, no charge.

Response

200 · application/json

{
  "films": [{
    "id": "7f2a…", "title": "Rooftop night",
    "scenes": 3, "updatedAt": "2026-09-11T14:02:11Z"
  }]
}