Using AI Streams from the API

Everything above can be driven from your own code with the Stream Repeater API. Create a token under Settings → API tokens (read-only, or read and write), then see the full reference at /docs/api and the OpenAPI file at /api/openapi.json.

AI Streams endpoints need AI Streams on your plan. Changes need a write token and the Manage streams permission in the workspace. You can only reach your own workspaces.

What you can do

• Create, update and delete streams — with the same checks as the form (provider, shape, clip length, channels, spend limit). A new stream is never switched on; call start.
• Start and stop a stream.
• Beats — add, edit, delete, and cue one to play next.
• Schedule — add, edit and delete weekly or one-off blocks.
• Push a topic now — make the stream about something that just happened.
• Read why a stream is or isn't generating (the same answers as the banner), recent clips, which channels are receiving it, its schedule, which providers are connected (never the keys), and the days saved to your Video Library, with download links.

Provider keys can only be added on the dashboard.

Example: push a topic when something happens

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

The topic takes over for the minutes you give (30 if you don't say), then the stream goes back to its running order where it left off. It doesn't jump the queue: clips already made play first, and the reply says how many (clips_ahead). It doesn't start a stopped stream either.

Webhooks and automations

Developer webhooks (Settings → Developer webhooks) and automation rules (Integrations) can react to AI stream events: a stream switched on or off, a stream pausing for a live broadcast, a channel dropping out, a provider refusing a key or running out of credit, and a day's video being saved.