TRaX Docs
reference

Stream paths

Every feed in TRaX lives at a path — the routing key shared by all protocols (the SRT streamid path field, the RTMP URL path, the WHIP/WHEP URL path) and bound into every session token's path claim.

The public grammar

External contributions are provisioned as input paths:

inputs/<type>-<uuid>
  • <type> — the input kind assigned at provisioning (for example srt, rtmp).
  • <uuid> — the input's unique id.

You receive the exact path when your input is provisioned; treat it as opaque. Paths are exact-match — there is no wildcarding, no trailing-slash tolerance, and case matters.

Rules

  1. The path in the URL and the path in the token must be identical. The token binds action + path; any difference is an auth failure, not a 404.
  2. Don't construct paths yourself. Other path families exist on the platform for internal use (studio program feeds, participant devices, monitoring). They are not contracts and reject external credentials — only the inputs/... path you were provisioned is yours.
  3. Budget for the path in SRT. The path is part of the streamid, which has a 512-byte hard cap — another reason not to invent long paths.