Guides
Your first video in one sitting: from raw clips to a finished cut
Sign up, answer two questions, drop in your clips, say what the video is for and press Run. What to expect from a first ReelBolt video, limits included.
· 9 min read
ReelBolt 0.3.1-alpha — public alpha. Expect rough edges; things may change. Tell us what’s wrong
We collect telemetry to see how the alpha is going. We also record product-health signals (a failed tool call, a refused request, a failed workflow step, or a chat that ended on an error) as metadata only, so we can see when the alpha is struggling. Each is linked to your account and workspace, and so to your email address; it is not anonymous. It carries no message content. Privacy policy
Guides
Create an API key, start a run from your own script, and get a signed webhook when it ends. What the ReelBolt API does today, and what is still alpha.
Published · 5 min read
If your videos start somewhere else, such as a content calendar, a product catalogue or a script you already run, opening the dashboard to press Run gets old fast. The ReelBolt API lets your own scripts and services do what you do in the app: upload files, create a workflow from a template, start a run, follow it and download the result.
Webhooks close the loop. Instead of asking again and again whether a run is done, your server gets a message when it ends.
An Owner or Admin of the workspace makes an API key on the API keys page. You give it a name and pick its scopes. A key can do only what its scopes allow, so a script that only reads results gets only read access. A key never gets administrator rights, and it cannot reach workspace settings, billing or members.
You can also limit a key to chosen projects, so it sees nothing else, and set an expiry. If you set one, ReelBolt mails a warning a week before and again a day before. The key list marks keys with no expiry and keys nobody has used for 30 days, so you can clean up.
The secret starts with rbk_ and is shown once. ReelBolt keeps only a fingerprint, so it cannot show it again. Scopes, projects and expiry cannot be edited after you create the key. If something needs to change, make a new key and revoke the old one. Revoking works immediately.
Keep the secret on your server, never in browser or mobile code or in a repository. If it leaks, revoke it and create a new one.
A run start takes the same run request the dashboard sends. You can ask for an estimate first and confirm the cost you saw when you start. Then you can read the run’s status, its steps and its credits, stop, resume or retry it, and list its outputs. An output comes as a link that works for 15 minutes.
Runs started this way cost the same credits at the same prices as runs started in the dashboard. Each key can have a daily, weekly or monthly credit cap, so a script that goes wrong cannot spend the whole balance. Each key can also make 300 requests a minute, and a start over the hourly run limit is queued instead of refused.
You give ReelBolt a public https address and the events you want. By default you get run.succeeded, run.failed and run.cancelled. Each message includes the run, the project, the status, a failure code if there is one, and the credits charged.
Every message is signed, and the format follows the Standard Webhooks convention, so existing libraries can check it. The signing secret starts with whsec_ and is shown once. You can rotate it later, and for 24 hours both the old and the new secret work, so you can deploy without missing an event.
If your server does not answer in time, ReelBolt tries again, for about a day in total. An endpoint that only fails for 3 days is switched off, and the workspace Owners and Admins get a mail. In the dashboard you can see the delivery log for an endpoint, send a test event, and send any delivery again. Deliveries are kept for 30 days.
The API is available on paid plans, Creator and up. A trial workspace gets a clear refusal when it tries to create a key. The API guide lists which plans include it.
ReelBolt is in alpha, and the API may change as we learn how people use it. Build with that in mind: read the guide before you rely on a detail, and keep a key’s scopes small.
The API guide has a short quick start, from creating a key to fetching an output link. For the details, see Keys and Webhooks, and Runs for starting and following a run.
Only Owners and Admins of a workspace create, see, change and revoke keys. The secret is shown once, when you create the key, so copy it then. If you lose it, create a new key and revoke the old one.
The API is available on paid plans, Creator and up. On a trial workspace, creating a key is refused with a clear message. The API guide lists the plans that include it.
You can change its name and its credit caps. Scopes, the project list and the expiry cannot be edited, so to change one of them, create a new key and revoke the old one.
No. Runs started through the API cost the same credits at the same prices as runs started in the dashboard, and they draw from the same workspace balance. You can also give each key a daily, weekly or monthly credit cap.
By default, run.succeeded, run.failed and run.cancelled. You can also ask for an event when each step finishes, and for events about queued starts. The address must be a public https URL.
Not yet. ReelBolt is in alpha, and the API may change. Check the API guide before you build something that depends on a detail.
See it on your footage
Drop in your clips and say what the video is for. An AI video team makes the first cut, you change what you want, and every paid step shows its estimate first.
Guides
Sign up, answer two questions, drop in your clips, say what the video is for and press Run. What to expect from a first ReelBolt video, limits included.
· 9 min read
Guides
Only an idea and no footage yet? Film five ten-second clips on your phone: the opening, the person, the thing, the detail and the close. Then turn them into a video.
· 8 min read
Guides
For coaches, teachers and course makers: cut a recorded lesson into short captioned clips, add translated subtitles or a dub, and know the limits before you start.
· 13 min read