Realtime Videos

Authentication

Realtime sessions use the same tf_ API key as the rest of the API, with one extra concern: the media goes to a client.

Key format, revocation, and storage are covered in Authentication. This page covers what is different for realtime.

Keeping the key off the client

Create sessions from your server and hand the browser only what it needs. The signaling proxy lives under the session URL and requires the same bearer key, so today a browser client that talks to it directly would carry your key.

Realtime-specific errors

StatusMeaning
401Missing, malformed, or revoked key.
404The session does not exist, or belongs to a different key.
← QuickstartSessions →