Schedule recurring Uscreen live streams

1. Open Content > Live Streaming in the Uscreen admin, find last week's session, click the ellipsis (...) and choose Duplicate.
2. In the Duplicate modal, set the title, start date, URL handle and stream key option; Uscreen fills the start date with the current date and time, so it has to be changed every time.
3. Choose whether to reuse the stream key or generate a new one; a new key has to go into OBS or other streaming software before the session starts.
4. On the new event, open the Preregistration card, turn on "Email preregistered attendees when the event starts" (older stores still show "Send email notification when event starts"), set Visibility to Published and click Save Changes.
5. Repeat for every session. Uscreen does not carry preregistrations over to a duplicate, so members register again each week, and a week nobody duplicated only shows up when members find no event to join.

Create the Thursday 18:00 Q&A live stream for the next four weeks over RTMP, with live chat and preregistration on, and send me the stream URL and key for each date.

1. 01

   Find the series and what exists

   The agent reads list_live_events with the series title and notes the last session's method, start time and settings. Dates that already have an event are skipped, so running the job twice never puts two Q&As on the same Thursday.

2. 02

   Plan the dates you asked for

   Sessions are placed at the same local start time in each week of the window you name, and dates you mark as off (a holiday, a trip) are left out. Two sessions closer than an hour apart are treated as a mistake and sent back to you.

3. 03

   Create each session with your OK

   create_live_event runs once per date with live chat and preregistration as the earlier sessions had them. Each call waits for your confirmation unless you switched that off, because a published event with a countdown is visible to members at once.

4. 04

   Hand over keys date by date

   For RTMP sessions, create_live_event returns the stream URL and key of each new event, and the agent lists them next to each date. When you asked to reuse one key, it checks that sessions on that key sit at least 5 minutes apart, the gap Uscreen requires. For other methods it names the method per session instead.

5. 05

   Point at what Duplicate would have copied

   Duplicate in Uscreen copies pricing options, assigned plans and access settings from the source event. create_live_event builds each session from scratch, so the agent says so in the report and lists the event IDs whose Purchase and Access Options you should check before the first session.

Thursday Q&A, 4 sessions created over RTMP, live chat and preregistration on:
5 Nov 18:00, event 77310. 12 Nov 18:00, event 77311.
19 Nov 18:00, event 77312. 26 Nov skipped: you marked it as off.
3 Dec 18:00, event 77314.
Stream URL and key listed per event below; keep them private.
Check Purchase and Access Options on 77310 to 77314: they were not copied from last week.

• Uscreen does not carry preregistrations over to a duplicated live event, and viewers cannot withdraw a preregistration once they have made it.
• Uscreen counts Live Studio and RTMP streams against the plan's monthly live streaming hours, while Zoom and Custom CDN (HLS) streams do not; going over the hours does not stop a stream but is billed as overage.
• Uscreen lets a stream key be reused for later events but asks for at least 5 minutes between events on the same key.
• Uscreen saves each RTMP recording to Content > Videos as an unpublished video, and it does not record Zoom streams automatically.
• Uscreen preregistration sends a confirmation email and, if enabled, an email when the event starts; the help center lists no reminder in between.

create_live_event asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: Uscreen Help Center: Duplicate a Live Stream · Uscreen Help Center: Live Stream Preregistration · Uscreen Help Center: Live Stream with Stream Software (RTMP) · Uscreen Help Center: Live Streaming on Uscreen, Choose Your Method

curl https://cotlet.dev/api/v1/uscreen/create_live_event \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Thursday Q&A","start_at":"2026-11-05T18:00:00-05:00","method":"rtmp","live_chat":true,"preregistration":true,"publish":true}'

{
  "event_id": "77310",
  "title": "Thursday Q&A",
  "start_at": "2026-11-05T18:00:00-05:00",
  "method": "rtmp",
  "status": "published",
  "preregistration": true,
  "live_chat": true,
  "stream_url": "rtmp://live.example.com/app",
  "stream_key": "sk_example_4f9a21"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is uscreen_create_live_event. Example data.

• Build a Uscreen course collection with week dividers and drip
• Schedule a batch of Uscreen video releases
• Uscreen API and MCP server: every tool
• All use cases