RTMP Stream Keys on Mobile: Connect Any Destination from Your Phone Dashboard

Every multistreaming guide eventually hits the same wall of jargon: RTMP URL, stream key, ingest endpoint. None of it is complicated — it is just never explained in one place. This is that place. By the end you will know what these strings do, where each platform hides them, and how to manage them from your phone without pasting secrets into random apps.

What RTMP actually is

RTMP (Real-Time Messaging Protocol) is the delivery protocol most live platforms still accept for ingest. A destination is defined by two strings:

• The RTMP URL — the server address your video upload streams toward, for example rtmp://live.twitch.tv/app.
• The stream key — a secret code that identifies your specific channel on that server. Anyone holding it can broadcast as you, so treat it like a password.

King Push stores keys encrypted at rest and never displays a full key after you save it — you will see only a masked hint.

Where to find each platform's stream key

Twitch

Creator Dashboard → Settings → Stream. Primary stream key sits at the top; copy it once and paste it into King Push's Add Channel form along with Twitch's RTMP URL.

Facebook

Meta Business Suite → Live Producer → "Use stream key". Facebook rotates continuous-use keys if you reset them, so re-paste after any reset.

Kick, Kick-alternatives and custom boxes

Any RTMP-compatible server works: Kick's Creator Dashboard, a self-hosted MediaMTX or nginx-rtmp instance, even a SRS box on a home server. Paste the URL and key, name the destination, and it appears on your director board with full telemetry — bitrate, dropped frames, viewer count where the platform exposes it.

Managing keys from a phone dashboard, safely

• Paste, do not type. Mobile typos in a 40-character key cost you a half hour of debugging a black screen.
• One destination per entry. Do not reuse one key across two entries — reset cycles will silently break one of them.
• Reset keys when a device is lost. Every platform has a reset button; after a reset, update the single entry in King Push and nothing else changes.
• Test before showtime. King Push's pre-flight check handshakes each RTMP destination so a bad key fails in settings, not live.

Troubleshooting: the three usual suspects

Black screen, no error

Almost always a stale key after a platform reset. Re-copy the key and save the destination again.

Connects, then drops at ~30 seconds

Upload bandwidth. Drop the destination's ceiling to 720p30 in King Push's per-destination settings — the rest of your destinations keep full quality.

Viewers see the stream, director board shows offline

Some custom servers do not expose status telemetry. The broadcast is fine; the board just cannot see inside. Add a viewer-side check for those destinations.

RTMP is plumbing: boring once it works, catastrophic when it does not. Set it up once in a phone dashboard that stores keys properly, and stop thinking about it.