Developers
One step in your pipeline
Your pipeline tells Caster a deploy happened. Caster records the videos again. It never needs access to your repository or your CI.
Update on deploy
Put your videos in a project, switch on automatic updates for the ones to keep fresh, and call one endpoint after each deploy. It works from any CI system.
# After a production deploy: record again and make the new versions live
curl -X POST https://caster.bot/v1/projects/$PROJECT_ID/deployments \
-H "Authorization: Bearer $CASTER_API_KEY" \
-H "content-type: application/json" \
-d '{ "publish": true }'
# After a preview deploy: record against the preview, keep for review
curl -X POST https://caster.bot/v1/projects/$PROJECT_ID/deployments \
-H "Authorization: Bearer $CASTER_API_KEY" \
-H "content-type: application/json" \
-d '{ "previewUrl": "https://pr-123.preview.example.com" }'GitHub Action
The same call, wrapped for GitHub. It can also record a new video of what a pull request changes and comment it on the pull request.
# .github/workflows/caster.yml
name: Caster
on:
deployment_status: # Vercel, Netlify, Render… report deploys here
permissions:
pull-requests: write
jobs:
videos:
if: github.event.deployment_status.state == 'success'
runs-on: ubuntu-latest
steps:
- uses: caster/action@v1
with:
api-url: https://caster.bot
api-key: ${{ secrets.CASTER_API_KEY }}
project-id: YOUR_PROJECT_ID
mode: rerecord
preview-url: ${{ github.event.deployment_status.environment != 'Production' && github.event.deployment_status.environment_url || '' }}
publish: ${{ github.event.deployment_status.environment == 'Production' }}Record from your own tools
Everything in the app is available over the API. Create a video from a support ticket, a script or an internal tool, and have the result sent back to a callback address.
curl -X POST https://caster.bot/v1/demos \
-H "Authorization: Bearer $CASTER_API_KEY" \
-H "content-type: application/json" \
-d '{
"url": "https://app.example.com",
"prompt": "Open Settings, then Team. Click Invite and enter an email.",
"formats": ["landscape-1080p", "gif-preview"]
}'Webhooks
Caster tells your systems when a recording starts, completes or fails. Every delivery is signed, and failed deliveries are retried.
POST https://your-server.example.com/caster
Caster-Event: version.completed
Caster-Signature: t=1763200000,v1=<HMAC-SHA256 of "t.body" with your secret>
{ "event": "version.completed", "demo": { "id": "…", "name": "…" }, "version": { "status": "succeeded", "renditions": [ … ] } }Safe to retry
Create endpoints accept an Idempotency-Key header. Send the same key twice and you get the first response back, not a second recording.
Preview and production
Preview deploys record against the preview address and wait for review. Production deploys record at the real address and can go live.
Keys per workspace
API keys are created in Settings, shown once and revocable. Only a hash is stored.
Live progress
Follow any recording as it runs over server-sent events, or wait for the webhook.
Add the step, forget the videos
Once the pipeline step is in, nobody has to remember to re-record anything.