Do you have API docs? I am running my own self hosted front end stream software, my software connects to zap stream backends. I want to see if I can add your backend to it.
Looks like an interesting project, I like streaming to nostr and twitch sometimes
chatgpt told me I can do it without API docs, I'm gonna see try ur service in the next couple weeks, thanks
Good luck. Let me know how it goes.
I tried Simulcast and it works great, I only tired one single stream because I don't have NWC, but my stream went well.
Super smooth sign up and setup. I understand now, it’s not a backend like Zap Stream but more like a bitcoin-friendly Restream. Really cool. Nice work
I'm glad you had such a good first experience. Thank you trying it out. Are there any features you would like to see added?
Yeah, one thing that would be cool in the future is some kind of public playback URL or HLS endpoint for each live stream.
Something simple like /stream/{id}.m3u8 that apps or websites could embed.
Not urgent, but it would open up a lot of integrations because Im also building a small streaming project for my own site, and having a simple public playback URL would make it easier to integrate external sources like yours. Nothing complex, just something that tools can read when a stream is live.
You should be able to embed the HLS Playback url that is available on the dashboard. Maybe I'm misunderstanding the request.
nice, yeah I saw the hls playback url in the dashboard and it works great when I paste it into a player manually.
What I was thinking of is something a bit more integration friendly, like a simple Jason/api endpoint or a stable url pattern that external tools can hit to get the current playback URL + live/offline status, without me needing to copy it from the dashboard each time.
just thinking ways self-hosted sites could hook into Simulcast, I'm new to this so I'm having a hard time understanding all this, trying to learn it
I think it's ready.
yaa, that's good news. I've been working to get it going already, I’m integrating simulcast into a self-hosted web player using hls . js
The status API works correctly through my server proxy. When a stream is live, the API returns something like:
{
"isLive": true,
"hlsUrl": "https://simulcast.me/hls/.../index.m3u8?apiKey=..."
}
If I open the hlsUrl directly in a browser, I see a valid HLS manifest (#EXTM3U, segment_XXX.ts, etc.), so the HLS pipeline itself is working.
However, when hls . js inside my web player tries to load that same URL, I get:
HLS error: manifestLoadError
This usually happens when the HLS endpoint does not send CORS headers, preventing browsers from fetching the manifest via XHR/fetch.
Would it be possible to enable CORS on the HLS endpoints (for example, Access-Control-Allow-Origin: *)?
This would allow web players using hls . js to load the manifest and segments correctly.
Give it another try. Thanks for testing it and finding the errors I missed.
no problem, I've been testing all other stream services, happy to help,
I tested the hls stream again after your change.
The good news, my web player can now request the manifest, so cors is definitely working.
However, I’m seeing a few new issues when streaming from OBS,
The stream comes online, then drops offline
Sometimes it appears in the player for a moment, then the player reports the stream as offline again. A few seconds later it may come back, then drop again.
hls buffer append error & Autoplay failed: DOMException: The fetching process for the media resource was aborted
hls buffer append error
It looks like the manifest loads correctly, but some of the .ts segments might be failing intermittently, which triggers hls . js to treat the stream as broken and drop back to “offline.”
summary
OBS to Simulcast detects “stream online”
Player starts loading segments
Buffer append fails intermittently
hls . js recovers - fails - recovers - fails
(stream flickers online/offline)
