Webhooks
Be told when a render is ready or has failed, so there's nothing to poll. Works with Zapier, Make and n8n.
A video takes a minute or two to make. Instead of asking again and again, give the render an address and we send you the result when it's done.
Ask to be told
Add webhook to the request that starts the render:
curl https://sitebrite.app/api/v1/renders \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"brand": "cm9x2brand0001",
"template": "quote-reel",
"modifications": { "quote": "Honest people.", "count": 214, "label": "happy clients" },
"webhook": "https://example.com/render-done?order=1042"
}'
- The address must start with
https://and be a public website. We check it before anything starts or is charged, so a mistyped address is a400, not a lost video. - Anything after the
?comes back to you. Put your own reference there (a spreadsheet row, an order number) and you'll know which video it is. It can be up to 500 characters in all.
When it's sent
We check renders that have a webhook about every 15 minutes, so you hear within about 15 minutes of the video being ready.
To hear sooner, also ask for the render with GET /renders/{id}. Any request for a render that has finished sends its webhook straight away. It is still sent only once, however you hear first.
What we send
A POST with a JSON body, one of two events:
type | When |
|---|---|
render.ready | The video is made and saved. data.url is the MP4. |
render.failed | It couldn't be made. data.url is null, and nothing was charged. |
{
"id": "cm9x2render001",
"type": "render.ready",
"created": "2026-10-29T18:01:12.000Z",
"business": { "id": "cm9x2brand0001", "name": "Main Street Bakery" },
"data": {
"id": "cm9x2render001",
"status": "ready",
"brand": "cm9x2brand0001",
"template": "quote-reel",
"ratio": "9x16",
"seconds": 8,
"cents": 0,
"url": "https://…/quote-reel.mp4",
"bytes": 1482113,
"error": null,
"createdAt": "2026-10-29T18:00:00.000Z",
"finishedAt": "2026-10-29T18:01:12.000Z"
}
}
data is the same render GET /renders/{id} gives you, so code that reads one reads the other. We add fields over time and never rename or remove one.
The request also carries these headers:
| Header | What it holds |
|---|---|
Webhook-Id | The render's id. The same on every try. |
Webhook-Event | render.ready or render.failed. |
Webhook-Signature | Proof it came from us. See Check the signature. |
Answer with a 2xx
Answer within 5 seconds with any 2xx status, and we're done. Anything else is a failure, a redirect included, and we try again after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, six tries in all. After that we stop.
We deliver at least once. If your address answers late, you may get the same event twice, with the same id. Keep the ids you've handled and ignore a repeat.
Check the signature
Anyone who learns your address could send to it. If it posts or charges anything, check that a request is ours first. Every request is signed with your account's secret, which you can ask for:
curl https://sitebrite.app/api/v1/webhook-secret \
-H "Authorization: Bearer $API_KEY"
{ "secret": "whsec_…" }
It's the same for every key on your account, and asking again gives the same one. Keep it as private as a key, and keep it on your server.
The signature is made exactly as it is for the dashboard's webhooks, so the code on Check the signature works as it is: use the secret from above, and the raw body of the request.
Zapier, Make and n8n
These tools can't check signatures, and don't need to: the address they give you is the secret, so treat it like a password. You'll make two small automations, one that starts the render and one that hears the result.
1. Make the receiver first, so you have an address to give.
| Tool | Receiver | The address you copy |
|---|---|---|
| Zapier | A Zap that starts with Webhooks by Zapier › Catch Hook | The custom webhook URL |
| Make | A scenario that starts with Webhooks › Custom webhook | The address Make shows when you add the webhook |
| n8n | A workflow that starts with a Webhook node, method POST | The Production URL, not the Test URL |
Add your own steps after it: post data.url to Instagram, send it by email, save it to Drive.
2. Start the render from anything: a new spreadsheet row, a form, a schedule. Add a step that sends an HTTP request:
| Tool | Step |
|---|---|
| Zapier | Webhooks by Zapier › Custom Request |
| Make | HTTP › Make a request |
| n8n | HTTP Request node |
Set it up the same way in each:
- Method and address:
POSTtohttps://sitebrite.app/api/v1/renders - Header:
Authorizationwith the valueBearerand your key - Body: JSON, as in the example above, with
webhookset to the address you copied
3. Teach the receiver what to expect. The first time, run step 2 once and let the receiver catch a real request. Zapier, Make and n8n each use it to list data.url, data.status and the rest as fields for the steps after it.
A few things that catch people out:
- n8n's Test URL only works while you're pressing Listen for test event. Use the Production URL and turn the workflow on.
- Zapier's Catch Hook address only works once the Zap is on.
- If the receiver is off when a video finishes, we retry for about nine hours before we stop. See Answer with a 2xx.
- Send the key from a step in your own account only. Never share a workflow that holds it.