Skip to content

API overview

The Reignitor API lets your servers make videos. You send a brief or a scene plan, Reignitor renders the video, and you collect the finished MP4. It is the same render engine that runs Brand Flow in the app.

  • Make a video from a brief. Describe the advert or training video in plain language. Reignitor plans the scenes and renders them.
  • Make a video from your own scene plan. Send the scenes yourself when you need full control over what each one shows and says.
  • Brand every video. Name one of your brand kits, or send a logo and colours.
  • Track renders. Poll a job until it finishes, or get a webhook when it does.
  • Check your account. Confirm a key works and read your credit balance.
https://reignitor.com/v1

Webhook subscriptions live under https://reignitor.com/api/webhooks and use the same API key.

  • Send JSON with Content-Type: application/json.
  • Every response is JSON, including errors.
  • Renders run in the background. Starting one returns 202 Accepted and a job_id straight away.
  • Call the API from your server. Never put an API key in a browser or mobile app.

Every request needs an API key in the Authorization header:

Authorization: Bearer emp_...

See Authentication for how to create and revoke keys.

API access is part of the Agency plan. A key on any other plan is refused with 402 PLAN_UPGRADE_REQUIRED. See Account and billing to change plan.

Renders spend your account’s credits, the same credits you use in the app. Every render response tells you how many credits it used, and GET /v1/me returns your balance. Credit costs depend on the length, scene count and quality of the video. See Account and billing for how credits work.

Method Path What it does
GET /v1/me The key’s account and credit balance
POST /v1/render Start a render from a brief or a scene plan
GET /v1/job/{id} Status of a render, and the video URL when done
GET POST PATCH DELETE /api/webhooks/... Manage webhook subscriptions