TRaX Docs
guides

Getting started with TRaX

TRaX is a browser-based live production platform: an OBS-style scene canvas in the browser, multi-host shows, and simultaneous output to multiple destinations (Twitch, YouTube, Kick, Facebook, and any custom RTMP endpoint). Under the studio sits a media ingest plane that accepts and serves standard streaming protocols:

Direction Protocols
Push a feed into TRaX SRT, RTMP / RTMPS, WHIP (WebRTC)
Pull a feed out of TRaX WHEP (WebRTC), SRT

These protocol contracts are documented in the Reference section and are usable today with credentials provisioned for you by the TRaX team.

Building an app or integration?

Two dedicated guides cover programmatic access:

  • Developer API (/v1) — a live, versioned REST + JSON API (dev preview at api-dev.traxstreaming.live/v1): list your studios, read sources / destinations / stream status, with an OpenAPI spec you can generate a typed client from. Authenticated with a sk_live_… API key you mint yourself.
  • Build a client — for iOS / Android / desktop apps: the transport map (WebSocket to control a studio, WebRTC to publish and watch, REST for reads) and how a native app logs a user in with OAuth PKCE.

Media authentication

All access to the TRaX media plane (SRT / RTMP / WHIP / WHEP) is authenticated with short-lived ES256 session JWTs minted by the platform (our identity provider is OIDC-based). Today those tokens are minted for the TRaX studio application and for credentials an operator provisions by hand.

What that means for pushing and pulling media:

  • You can push and pull media today using credentials handed to you by the TRaX team (an operator-provisioned token or stream key).
  • You can verify any TRaX-issued token yourself against our published JWKS — see Authentication & session tokens.
  • A first-party app logs the user in with OAuth (PKCE) and uses that user token across the control and media planes — see Build a client.

Where to go next

  1. Authentication & session tokens — how every request is authorized, token claims, JWKS verification.
  2. SRT: the streamid contract — the most robust way to push a feed.
  3. RTMP / RTMPS — the most compatible way.
  4. WHIP / WHEP — browser-native, sub-second latency.
  5. Push a feed with OBS or ffmpeg — a 10-minute end-to-end win.