Creatomate Render API

Name: Creatomate Render API API
Brand: Creatomate Render API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo Processingbearer4 EndpointsREST

For Agents

Generate videos and images programmatically from Creatomate templates by submitting a render job and waiting for the finished file URL. Use it for automated social posts, ad variants, or templated media at scale.

Quickstart

Get started with Creatomate Render API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"render a video from a template"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Creatomate Render API API.

List the templates available in a Creatomate workspace with their IDs and names

Fetch the full definition of a single template, including its named modifiable elements

Start a render by passing a template ID with modifications, or by supplying a full RenderScript scene

Poll a render by ID to read its status, progress, and the URL of the finished video or image

GET STARTED

Start building with Creatomate Render API API

Explore with Jentic

View OpenAPI Document

Use for: Generate a 30-second product video from a Creatomate template with custom text and image, Render an Instagram story from a template and get the MP4 URL, List all video templates in my Creatomate workspace, Check the status of a render job I started two minutes ago

Not supported: Does not handle template authoring, asset hosting beyond the rendered output, or live video streaming — use for template-driven video and image rendering only.

Jentic publishes the only available OpenAPI document for Creatomate Render API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Creatomate Render API, keeping it validated and agent-ready. Creatomate is a render service that turns templates and parameter sets into produced videos and images, returning rendered assets that an application can ship to social channels, ad platforms, or storage. The API exposes operations to list and inspect templates, kick off a render with template substitutions or raw RenderScript, and poll a render's status to retrieve the final output URL.

Use Cases

Patterns agents use Creatomate Render API API for, with concrete tasks.

★ Templated social-media video generation

Produce one video per data row, such as a product feed or daily news headline, by calling POST /renders with a template ID and a modifications object that overrides text and image elements. Creatomate handles encoding and returns a hosted URL for the finished MP4, removing the need for an in-house ffmpeg pipeline.

Call POST /renders with template_id of the Instagram template, modifications setting Headline.text and Product.source, then poll GET /renders/{id} until status is 'succeeded' and return the url field.

Ad creative variants at scale

Generate dozens of ad variants from a single base template by submitting a render request per variant with different copy, imagery, or call-to-action elements in modifications. Creatomate runs the renders server-side so the agent only manages the variant matrix and the resulting URLs.

For 12 headline-image pairs, call POST /renders with the same template_id and a modifications object per pair, collect the returned render IDs, and poll each until completion.

On-demand image card generation

Render branded share cards or social images on demand by posting to /renders with an image template and per-request modifications. Useful for blog open-graph cards, certificate generation, or quote-of-the-day images where the rendered file is fetched and served by the calling application.

Call POST /renders with the share-card template_id and modifications setting Title.text and Author.text, then return the url field once the render reports succeeded.

Agent-driven content rendering through Jentic

Let an agent fulfil a 'render me a 15-second teaser with this script' request without code by routing through Jentic. The agent searches for a render operation, loads the Creatomate /renders schema, and submits the template ID with modifications; Jentic injects the bearer key from the vault and returns the polling endpoint to use.

Through Jentic, run search('render a video from a template'), load Creatomate POST /renders, submit template_id and modifications, then poll GET /renders/{id} via Jentic until succeeded.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for creatomate render api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/templates

List all templates in the workspace

GET

/templates/{id}

Fetch a single template definition

POST

/renders

Start a render from a template or RenderScript

GET

/renders/{id}

Get the status and output URL of a render

GET

/templates

List all templates in the workspace

GET

/templates/{id}

Fetch a single template definition

POST

/renders

Start a render from a template or RenderScript

GET

/renders/{id}

Get the status and output URL of a render

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Creatomate bearer keys are stored encrypted in the Jentic vault. Jentic applies the Authorization header at execution time so the raw key never enters the agent context, prompt, or trace logs.

Intent-based discovery

Agents search Jentic with intents like 'render a video from a template' and Jentic returns the Creatomate POST /renders operation along with its modifications schema, so the agent can submit a render without reading the Creatomate docs.

Time to first call

Direct integration: half a day to a day to wire up template lookup, modifications payloads, and render polling or webhook handling. Through Jentic: under 30 minutes to search, load schema, and submit a first render.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shotstack

Cloud video editing and rendering API with a similar template-and-render model.

Choose Shotstack when the agent needs JSON-driven timeline editing primitives; pick Creatomate when work is anchored on visual templates designed in its editor.

Alternative

Bannerbear

Templated image and short video generation API focused on social and marketing assets.

Use Bannerbear for image-heavy automation and simple animated outputs; use Creatomate when richer video templates and longer renders are required.

Complementary

Cloudinary Upload

Asset upload and transformation API often used alongside templated render output.

Use Cloudinary to host or further transform the MP4 or PNG that Creatomate produces, then return the optimised URL to downstream consumers.

FAQs

Specific to using Creatomate Render API API through Jentic.

Why is there no official OpenAPI spec for Creatomate Render API?

Creatomate does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Creatomate Render API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Creatomate Render API use?

The API uses HTTP bearer authentication. Pass your Creatomate API key in the Authorization header as 'Bearer <key>' on every request. Through Jentic, the key is stored encrypted in the vault and applied at execution so it never enters the agent's prompt.

Can I render a video from a template with the Creatomate Render API?

Yes. Call POST /renders with a template_id and a modifications object that overrides the named elements in that template. The response contains a render id; call GET /renders/{id} to poll until status is 'succeeded' and read the output URL.

How do I get notified when a Creatomate render finishes?

Pass a webhook_url field in the POST /renders body and Creatomate will POST the completion event to that URL when the render reaches a terminal state, instead of requiring continuous polling of GET /renders/{id}.

What are the rate limits for the Creatomate Render API?

Creatomate enforces concurrency and monthly render quotas tied to the workspace plan rather than fixed per-second limits in the spec. Build retries around 429 responses on POST /renders and use webhooks instead of tight polling on GET /renders/{id} to stay within plan limits.

How do I render a video through Jentic?

Install Jentic with pip install jentic, then async-search for 'render a video from a template'. Load the Creatomate POST /renders operation, execute with template_id and modifications, and poll GET /renders/{id}. Jentic attaches the bearer key automatically.