Build on Stream Repeater

What you can build

Authenticate with a personal access token (read or read/write), scoped to your workspaces. Every endpoint returns JSON, and secrets like connection tokens and action payloads never get exposed.

The programmable trigger

The good bit: fire a custom event and every matching automation rule runs its actions. A donation page, your own backend, or a Zap can now drive what happens on stream.

# Fire a custom event — runs every rule listening for "custom.donation"
curl -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" \
  -d '{"type":"custom.donation","context":{"name":"Ada","amount":"5.00"}}' \
  https://streamrepeater.com/api/tenants/1/events

{ "ok": true, "matched_rules": 2 }

AI Streams

Drive an always-on AI video channel from your own systems: create a stream, write its running order and schedule, and push a topic in the moment something happens. Topics take over for as long as you say, then the story carries on where it left off — through the same content check and spend limit as everything else. (AI Streams is in development and not yet on a plan you can buy.)

# Something just happened — make the channel about it for 10 minutes
curl -X POST -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" \
  -d '{"instruction":"Fans erupt as the home side scores","minutes":10}' \
  https://streamrepeater.com/api/v1/tenants/1/ai-streams/5/topic

{ "ok": true, "on_air_now": true, "clips_ahead": 2, "message": "The next clip this stream commissions will be about this topic. …" }

# Why is it quiet? The same answer the stream page gives.
curl -H "Authorization: Bearer YOUR_TOKEN" https://streamrepeater.com/api/v1/tenants/1/ai-streams/5/status

All AI Streams endpoints · How AI Streams works

What people build