API Requests

Dear Restream Developer Team, I hope this email finds you well. My name is Muzzamil Ali, and I am a full-stack software developer currently building an application designed to help clients manage multi-platform live broadcasting seamlessly. I am looking into utilizing Restream's infrastructure and API to facilitate streaming to multiple platforms, with a specific interest in handling TikTok Live integrations. Could you please provide guidance on how developers can properly access and configure the Restream API for multi-platform broadcasting, or point me toward the right documentation and onboarding steps for developer accounts? Project Overview: Developer Name: Muzzamil Ali Use Case: Multi-platform live stream distribution and management for clients (including TikTok integration via Restream) Tech Stack: Node.js, React, WebSockets, RTMP protocols Thank you for your time and assistance. I look forward to hearing from you

Customer asked if Local Recording files, including separate per-participant tracks, can be downloaded via the Restream API. Current confirmed workflow requires the host to download these files manually from Studio under Download → Local Recordings after the session. Public API docs appear to support standard event recordings / storage files, but not Local Recording tracks specifically. Use case: customer plans to run many recording-only events and wants to automate post-production by programmatically downloading each participant’s local recording files instead of manually exporting them from Studio. Request: add a public API endpoint to access/download Local Recording files and individual participant tracks.

We are building an internal automation dashboard to manage the pre-production of our weekly live shows (we produce 2 shows a week). While the Restream Events API is great for scheduling, the Studio remains a manual bottleneck. We need the ability to programmatically prepare the visual layout of a show before going live - to be able to completely set up the entire "Run of Show" without clicking the Studio interface (which has become too slow of a process for us; we have a complex recurring show structure - 16 specific scenes including intros, guest segments, and sponsor slots). Key Use Cases: 1) Automated scene prep: creating or duplicating a "Show Scene Template" for a specific event (we are planning to schedule Restream events programmatically via the API, and we need the new event to be cloned from a specific draft). 2) Dynamic overlays: pushing specific "Lower Thirds" / captions to specific scenes via API based on guest data. 3) Sending media to specific scenes: Uploading event-specific assets (transparent PNGs/branded overlays) and adding them to a specific scene. 4) Elements ON/OFF on the scene: commands to toggle visibility of specific elements, such as specific tickers or captions on specific scenes. 5) QR Codes creation: we are creating a new QR code per each live stream now, manually. We want to automate this so that when we schedule a guest, their "Upper right/left QR" and "Live Sales QR" are automatically generated and placed in the Studio.

Restream used to be able to do this, but then y'all updated the platform and it no longer can. Every single time I go to start a new stream, it loads default copy instead of saving the copy I wrote. Overall the updates to the use of the platform have made it harder to use, and buggy. My live watch of it on Restream itself freezes every time, I also have to re-enter the restream key into OBS every single time I do a new stream. I don't know exactly what y'all did when you re-did Restream homepage, but it has been really annoying to use ever since. No more flow, no more fluidity, every stream set up takes longer than it ever did and it freezes and bugs out more than it ever did.

It is very good!

I don't know why after doing a YouTube live stream using restream when I watch the video offline the comments on YouTube don't appear

For /events/new it would be amazing to have it return inviteLink as an attribute alongside id. Id is fine for anything API related, but as data it is pretty much useless at the moment. I can do all sorts of GET functions with it, for which I have no need in any automation I do. /events/{eventId}/destinations does not support the destinations I stream to, so also irrelevant. Furthermore, with the duplicate event feature I requested in another post, I would not have to use the event Id at all, because most things would come preconfigured in the duplicate.