On Solo, Pro, Team and Agency plans. An Owner or Admin creates API keys.
Hand approved work straight to production, open projects as deals close, and fill storyboards from the shot lists and renders you already make.
When a storyboard is set to Approved, a task appears in Asana, Monday, ClickUp or Jira with the board name and review link. Nobody has to forward the sign-off.
storyboard.updated webhook in Zapier or Make.No code. Zapier or Make webhooks.
A deal marked won in HubSpot or Salesforce becomes a Boords project, named and described, before the kickoff call.
POST /v1/projects from an HTTP action, with your API key in the header.No code. An HTTP action in Zapier or Make.
Send a shot list from a sheet or your pipeline and Boords builds the storyboard, one frame per shot. Then push each render onto its frame as it finishes.
Needs code.
A REST API at https://app.boords.com/v1. Send a shot list as frames and the storyboard is ready for images and review.
Every request sends your API key in the X-API-KEY header. Each frame arrives with its label, sound and action filled in, and external_reference carries your own shot ID so later runs update the right frame.
curl https://app.boords.com/v1/storyboards \
-H "X-API-KEY: $BOORDS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"data": {
"name": "First Light (30s)",
"project_id": "p4k9az",
"frames": [
{
"label": "Laces",
"sound": "Nobody sees the first mile.",
"action": "Porch light on. Hands double-knot the laces.",
"external_reference": "SH010"
},
{
"label": "Empty street",
"sound": "No crowd. No finish line. Just you and the cold.",
"action": "She sets off down the terrace.",
"external_reference": "SH020"
}
]
}
}'Team webhooks fire when a storyboard changes status in Boords, such as a client approving on the review link, and for work done through the API or an AI connection. Personal webhooks carry your own comment notifications.
storyboard.updatedA storyboard moves to Approved, Changes Required or any other status, whether a teammate sets it or a client does on the review link, when reviewers can set the status. It also fires when the API or an AI connection updates a storyboard or reorders its frames, so filter on the status you care about.
notification.createdSomeone mentions you or replies to you in a storyboard comment, marks your comment complete or reopens it, or comments on a storyboard you follow. Comments made in the app count too. Each endpoint belongs to the person whose API key registers it, with one API call.
project.createdproject.updatedproject.archivedstoryboard.createdstoryboard.archivedscript.createdscript.updatedscript.archivedframe.createdframe.updatedframe.deletedcomment.createdcomment.updatedcomment.deletedChanges made by your own code, Claude or ChatGPT. frame.created also fires when the Boords Agent adds frames.
Boords posts JSON to your HTTPS endpoint. Trimmed here: the full payload also carries the frame fields, aspect ratio, cover image and edit link.
{
"id": "evt_3f9a1c0b7e2d4a6f8b1c2d3e",
"event": "storyboard.updated",
"occurred_at": "2026-10-17T10:42:08Z",
"data": {
"type": "storyboard",
"id": "s9bx1z",
"attributes": {
"name": "First Light (30s)",
"project_id": "p4k9az",
"status": "approved",
"frame_ids": [101, 102, 103, 104, 105, 106, 107, 108],
"public_url": "https://app.boords.com/s/k7m2qd8x",
"updated_at": "2026-10-17T10:42:08Z",
"archived": false
}
}
}X-Boords-Signature is a hex HMAC SHA-256 of the X-Boords-Timestampvalue, a full stop and the raw body, signed with your webhook’s secret. Boords does not reject old timestamps for you, so check them on your side.
import crypto from 'node:crypto'
// rawBody: the request body exactly as it arrived
const timestamp = req.headers['x-boords-timestamp']
const signature = req.headers['x-boords-signature'] ?? ''
const expected = crypto
.createHmac('sha256', process.env.BOORDS_WEBHOOK_SECRET)
.update(`${timestamp}.${rawBody}`)
.digest('hex')
const valid =
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))API keys and webhooks live on one page in Boords Settings.
project.created event so you can check your endpoint.X-RateLimit-Reset header says when to try again.notification.created event for the person it notifies. To see every comment, view and export, read the activity feed, GET /v1/teams/{team_id}/events, on a schedule; each request covers up to 90 days.Not for approvals or new projects. Zapier and Make can catch Boords webhooks and call the API with your API key, with no code. Turning a shot list or a render pipeline into frames needs some code.
No. Catch Boords webhooks with Webhooks by Zapier or a custom webhook in Make, and call the API from their HTTP actions with your key in the X-API-KEY header.
Yes, for your own notifications on storyboards: comments that mention you, reply to you or land on a storyboard you follow. Register a personal notification.created webhook with one API call using your own API key, or get them as Slack DMs with no code.
Yes. Send an Idempotency-Key header with a write and a repeat returns the first result instead of making a second copy. Resource writes also take If-Match with the ETag Boords returned, so you don't overwrite a newer change by mistake.
Solo, Pro, Team and Agency. An Owner or Admin creates API keys and team webhooks in Settings, under API & Webhooks.