TRaX Docs
guides

Our API philosophy

TRaX is API-first and community-friendly. The platform is a set of capabilities — studios, sources, destinations, going live, stream status, platform connections, chat, and media — and we want you to build on all of it. Apps, bots, dashboards, mobile controllers, full third-party "thick clients" that produce a show without ever opening our web studio: that's the point, not a side effect.

Open-by-default

Our default posture is to expose as much of the platform as we safely can. When we look at a capability and ask whether third-party developers should be able to use it, we treat that as the wrong question. The only question we ask is:

Can we offer this safely?

If a capability can be offered safely, the default answer is yes, expose it. We don't hoard surface area, and we don't make you screen-scrape the web app to do something the platform already knows how to do.

What "safely" means

"Safely" isn't a vibe — it's a checklist, and it's the only thing we gate on:

  • Authenticated. Every request carries an identity. You act as yourself using an API key you create, or your app acts on a user's behalf with their consent through OAuth.
  • Scoped. A credential can do only what its scopes allow, and never more than you can already do yourself. A read-only key stays read-only.
  • Isolated to your tenant. A credential can only touch resources that belong to it. It can never reach another account's studios, streams, or data.
  • Rate-limited. Every credential has fair-use limits so one integration can't degrade the platform for everyone else.
  • Leak-free. Our public surfaces never hand back another user's data or our internal plumbing.

Clear those, and we lean toward giving you the key.

Where this is going

Today the media ingest plane (SRT, RTMP, WHIP/WHEP) is a real, documented contract you can push and pull streams over — see the Reference section. The control-plane Developer API (/v1) is live in dev preview: list your studios, read sources / destinations / live status, with user-minted, scoped API keys as the first-class way to authenticate as yourself, and go-live / go-offline plus stream-event webhooks close behind. Building a mobile or desktop app? Start with Build a client.

Want to build something specific? Tell us — the roadmap follows what the community wants to build.