The stream-key ritual: Instagram, TikTok, and X before every stream

You can leave a connected YouTube or Twitch destination in place and use it again. Instagram, TikTok, and X often work differently: the platform creates a stream event and issues a fresh RTMP URL and key for that session. If you reuse yesterday’s credentials, the destination may reject the feed even though nothing changed in ApexStream.

Why the key needs to be fresh

These platforms use session-based stream keys. The key belongs to a particular live event rather than to your account forever. When that event ends, the credentials may no longer be valid for the next broadcast.

That is a platform rule, not an ApexStream setting. The multistream can be ready everywhere else and still fail on TikTok or Instagram because the destination is holding an old key.

Do the ritual before the countdown

1. Open the live-production area for Instagram, TikTok, or X.
2. Create the new live event and copy its current RTMP URL and stream key.
3. Return to ApexStream and remove the old Custom RTMP destination.
4. Add the destination again with the new URL and key.
5. Give it a Friendly Name that identifies the platform and session.
6. Check the destination count and test the connection before activating the show.

The source workflow does not currently include a self-serve key-rotation control. Removing and re-adding the Custom RTMP connection is the reliable way to replace the credentials.

Why the key is not requested in a go-live popup

A last-second popup sounds convenient, but the outgoing destinations are provisioned together when the broadcast starts. Waiting for a new key would delay the channels that are already ready, and it would make the launch depend on a platform page you may still be searching for.

Keep the update in the pre-show workflow instead. Fetch the keys while the countdown is still running or before you start the encoder. That way the YouTube, Twitch, and other destinations can begin on time while the mobile-first endpoints use the credentials for the current session.

Make the labels do useful work

Friendly Names matter when your dashboard contains several temporary connections. Use names such as “Instagram — July 23 show” or “TikTok — product demo” while you are preparing the session. After the show, remove stale entries so you do not accidentally activate an expired key next time.

Keep the key private. Treat it like a password for the live event, and paste it only into the intended destination fields.

Budget the destinations

These temporary connections still count toward the plan’s simultaneous-destination allowance: Free 2, Hobby 3, Creator 5, Scale 8, and Enterprise 50. If you use one slot for YouTube and one for Twitch, only the remaining slots are available for the fresh mobile-platform keys.

Do not let an expired destination occupy a slot in a rehearsal. Remove it, add the current connection, and confirm the right toggles before you go live.

The ritual takes a few extra minutes, but it is predictable: generate fresh credentials, replace the connection, label it clearly, and verify the far end. Once it is on the checklist, the session-based nature of these platforms stops being a surprise.