Create a stream and fill its playlist. Schedule it or go live. Switch scenes and swap videos while it runs. A plain REST API with one key, included with every paid plan.
# Go live on a project
POST https://api.livereacting.com/v1/external
/projects/{id}/live
Authorization: Bearer lr_your_api_key
# 201 Created
{
"liveId": "507f1f77bcf86cd799439011",
"status": "PREPARING",
"destinations": [{
"provider": "youtube",
"name": "My YouTube Channel",
"viewingUrl": "https://youtube.com/watch?v=abc123"
}]
}A project your code creates shows up in your LiveReacting studio like any other. Open it there at any time and change it by hand.
Read the API docs →Create a stream project, set the YouTube channel or other destination it streams to and how long it runs, and list its past broadcasts.
In the API docs →Start a stream now, or schedule one or several start dates up to 28 days ahead. Stop a running stream or cancel what is scheduled.
In the API docs →Swap a video or reorder the playlist while the stream runs, then push the change to the broadcast in one call. With auto-sync on, every change goes out at once.
In the API docs →Create scenes, switch the one on air, and chain them so the next comes on when a playlist ends. One workflow call builds a scene with its playlist and that rule.
In the API docs →Add video playlists, audio playlists and single videos. Replace their files, move and resize them, and play or stop one on a running stream.
In the API docs →Upload a file from your computer, or import one from a Google Drive, Dropbox, YouTube or direct link and check the import. Encode files, rename them in a batch, and list them by folder.
In the API docs →List the YouTube channels, Facebook pages, Twitch channels and your own destinations (custom RTMP) connected to your account, and check their tokens before you go live.
In the API docs →For each stream, pull its YouTube views, watch time and revenue, on every paid plan, and the log of which file played when, by request.
In the API docs →Four jobs a producer does by hand in the studio, done by a script instead. No one has to be in the studio when the stream starts, changes or ends.
A script on a timer imports each day's videos and adds them as a new scene. The stream switches to it when the current playlist ends.
See the four steps →Your scheduler creates a project from the recording and books the start times, up to 50 of them, 28 days ahead. A lesson or a demo goes out live without you.
In the API docs →An agency with many client channels builds one screen of its own. Every stream with its status, start and stop for each, and a playlist swap pushed to the live stream.
In the API docs →A scoreboard, a content system or a chat bot switches the scene, plays a clip or swaps a video in the running stream. Auto-sync sends it out at once.
In the API docs →Your script imports the videos, creates the stream, adds a playlist scene and starts it. Tomorrow it adds a new scene, and the stream switches to it when today's playlist ends.
Read the daily rotation guide in the API docs →POST /files/import
One request per video, with its Google Drive, Dropbox, YouTube or direct link. Each file gets an id, and its import status turns to completed.
POST /projects
Pick the YouTube channel, Facebook page or other destination it streams to. Set the duration to manual, and the stream runs until you stop it.
POST /projects/{id}/scenes, then /layers
One request creates the first scene and makes it active. A second puts the imported files in its video playlist and sets it to loop.
POST /projects/{id}/live
The stream starts on every destination in the project. The response returns the stream id and each destination's watch link as soon as the platform creates it.
Connect Claude Code, Codex, Cursor or another MCP client that takes an API key. Ask in words, and the agent builds a stream from a playlist, starts it, schedules it and reads the broadcast history afterwards.
See AI agents (MCP) →Nothing on top of your subscription. API access is included with every paid plan, and an account on the Free plan cannot create a key. Plans and prices are on the pricing page.
Sign in to your LiveReacting account, open the Developer section, and create a key. It starts with lr_ and goes in the Authorization header of every request as a bearer token. An account can hold up to ten keys, and you can revoke any of them.
150 requests a minute for each account, shared by all of its keys. Every response says how many requests remain and when the count resets. If you need more, write to [email protected].
Yes. A change through the API edits the project, not the broadcast. Push it to the broadcast with the sync call when you are ready, or turn on auto-sync on the project and every change goes out the moment you make it.
It cannot connect a new YouTube channel, Facebook page or other destination. That happens in the studio, and the API only lists and checks the ones you have. It cannot create text, image or interactive layers. It reads them, and creates or edits video playlists, audio playlists and single videos only. And it cannot start a Plugin Mode project, the overlays you add to OBS or vMix.
No. This API controls streams built in the LiveReacting studio. To capture any web page and stream it, see the API for live streaming web pages.
Build your stream in the studio on the Free plan, which does not expire. Move to any paid plan when you are ready to automate it, and the API key comes with it.
Want the numbers first? See plans and pricing