Kick, Trovo, LinkedIn Live, X, Rumble, Odysee, Restream, Vimeo, your company's Wowza box, a self-hosted nginx-rtmp server. If it gives you an RTMP or RTMPS URL and a stream key, Streamza can send your video to it from the cloud.
Every RTMP destination is two pieces of text, and almost every failed stream is one of them in the wrong box.
The server URL identifies where to connect and which application on that server to publish to:
rtmp://live.example.com/app
The stream key is the private name your broadcast publishes under, and it doubles as your password:
live_123456789_AbCdEfGhIjKlMnOp
Some platforms hand you a single joined URL instead — rtmp://live.example.com/app/live_123456789_AbCdEfGh. If you get one of those, split it at the last slash: everything before it is the server URL, the last segment is the key.
RTMP or RTMPS? RTMPS is the same protocol inside a TLS connection, usually on port 443. Use whichever your platform gives you — some, like Facebook, require RTMPS. Streamza supports both.
| Platform | Where to look |
|---|---|
| Kick | Creator Dashboard → Settings → Stream. Kick shows both a Stream URL and a Stream key — copy both, since the URL is account-specific. |
| Trovo | Creator Center → Stream settings → copy the RTMP address and stream key. |
| LinkedIn Live | Available to Pages and profiles with Live access. Create the event, choose a third-party encoder, and copy the ingest URL and key. |
| X (Twitter) | Use X's producer tool to create a broadcast and copy the RTMP URL and key. |
| Rumble | Account → Live stream → copy the server URL and stream key. |
| Odysee / Owncast | Odysee: Livestream page → stream key. Owncast: your admin panel shows the RTMP URL and key you configured. |
| Vimeo | Create a live event → connect an encoder → copy the RTMP link and key. |
| Restream | Dashboard → RTMP settings. One key that fans out to every channel you have connected there. |
| Dacast, Wowza, Castr, Muvi | Each channel's publish or encoder settings page lists the ingest URL and key. |
| Self-hosted (nginx-rtmp, SRS, MediaMTX) | The URL is rtmp://your-server-ip/app and the key is whatever stream name you choose. Make sure the port is reachable from the public internet. |
YouTube, Twitch and Facebook do not need this page — their ingest URLs are already built in. See YouTube, Twitch and Facebook.
From your platform's encoder or stream settings page. Keep them separate; do not paste the joined form into one field.
At streamza.live/studio, claim a slot and pick the custom option so both fields become editable.
Server URL in the URL field, key in the key field. Watch for a stray space at either end — pasted keys pick them up constantly.
Then confirm the broadcast on the destination side if that platform requires it. Once it is running you can close the browser.
Custom RTMP is not only for consumer platforms. It also covers cases where you control the receiving end:
The one requirement is that the endpoint is reachable from the public internet. A server behind a firewall or on a private network cannot receive our stream — open the RTMP port, or use a publicly routable ingest.
Wrong host, wrong port, or the server is not accepting publishes. Check the URL character by character, and for self-hosted servers confirm the port is open from outside your network.
Usually authentication — an expired, mistyped or already-in-use stream key. Regenerate the key on the platform and try again.
The URL and key are probably swapped, or the key was pasted with the application path still attached. Split the joined URL at the last slash.
The port is likely wrong. RTMPS almost always runs on 443 and needs to be written explicitly, as in rtmps://host:443/app/.
Some endpoints impose their own session limits or idle timeouts. Check the destination's own broadcast limits.
Any platform that accepts an RTMP or RTMPS publish — which in practice is all of them. Kick, Trovo, LinkedIn, X, Rumble, Odysee, Vimeo, Restream, DLive, VK, enterprise servers and self-hosted setups all work the same way.
Yes, as long as it is reachable from the public internet. Point Streamza at rtmp://your-server/app with whatever stream name you want as the key.
Yes. Paste an rtmps:// URL and it connects over TLS, typically on port 443.
Split it at the last slash. Everything before it is the server URL; the final segment is the stream key.
Yes, up to three simultaneously on the Multistream plan — and they can be any mix of built-in and custom endpoints. See multistreaming.
Not currently. Streamza publishes over RTMP and RTMPS, which every major platform accepts. If your destination only takes SRT, you would need a gateway in front of it.
Paste the URL and key, and your video goes live wherever you need it.
