Skip to main content
GET
Every template has a different set of variables, so there’s no fixed request shape to look up statically — this endpoint computes it live from the template itself, every time it’s called, so it can never drift from what the template will actually do at generate time. Serves both kinds of template: video variables come from the template’s scenes, image variables from its layers. Without type you get video, exactly as before; pass type=IMAGE_TEMPLATE for an image template. Call this before building a Generate videos or Generate images request.
string
required
string
default:"TEMPLATE"
TEMPLATE or IMAGE_TEMPLATE — must match the kind of template template_id actually is, or the lookup returns 404. Same param as List templates.
string
required
Bearer {api_key}

Response fields

array
Every variable this template uses, each with name and an example_value pulled from the template itself.
string
Echoes back the kind of template this is — TEMPLATE or IMAGE_TEMPLATE.
string
Image templates only — what one row costs: one flat price per rendered image, the same whatever the template’s variable count. Multiply by your row count for the batch total. Absent for video templates, which carry the same figure as estimated_credits on the template itself instead.
object
A ready-to-use example, including one example row and the correct path for this template’s kind — /templates/{id}/bulk-generate/ for video, /image-templates/{id}/bulk-generate/ for images. Use a single-item rows list to generate just one.
A template with no variables at all returns an empty variables array, and bulk_generate.body reflects that (a single empty row) — you can still generate from it, every result just comes out identical.
credits_per_row is the template’s price as it stands right now. Treat estimated_credits in the Generate images response as the figure actually charged for a given batch.