What you can build with Glossa today
Glossa is a product first and a platform second. Six things are built to be integrated with, and all of them are available on every plan, including Pay As You Go and the free trial.
The six surfaces
Section titled “The six surfaces”- REST API: API keys you create in Settings, and read endpoints for your services, whether each one is live and who is listening, past sessions and transcripts, billed usage and the weekly recaps. The API reference lists every endpoint, and an OpenAPI document is published for Swagger UI, Postman and AI agents.
- Webhooks: signed HTTP POSTs to URLs you register in Settings when a session starts or ends, when its usage is computed, when listeners join or leave, and for every translated sentence (text and optionally the spoken audio). Good for a lobby screen, your own statistics, an archive, or n8n, Make and Zapier.
- Embed and iframe parameters: two framable pages, a captions-only view and the full listener page, styled through URL parameters.
- Captions overlay: the captions view used as a browser source in OBS or vMix, or as a web element in ProPresenter, for a lower third on your stream or screens.
- RTMP ingest and stream keys: send audio from OBS, vMix or a hardware encoder to
rtmp://stream.glossa.live:1935/livewith a per-service key. Transcription starts and stops with the encoder. - Widgets and QR codes: HTML snippets for your website and print-ready QR slides, all pointing at your permanent listener link.
What there is not, yet
Section titled “What there is not, yet”- No write or control endpoints. The REST API is read-only: it cannot start or stop a session or change a service. For hands-free start and stop use RTMP ingest, where the session follows your encoder.
- The app’s own endpoints are not an interface. Everything the dashboard does over HTTP is authenticated with the signed-in user’s session and answers only browsers on glossa.live origins; from another website those calls fail the CORS check, and they may change without notice. Use the REST API instead.
- No listener protocol documentation yet. Listeners connect over a WebSocket that is read-only for anyone who knows a service id. We can share the message format on request. Write to info@glossa.live with what you are building.
- No SRT ingest. The RTMP page explains the status.
Conventions used in these pages
Section titled “Conventions used in these pages”Every Developers page lists the source files it was derived from in its front matter, and the embed parameter table is checked against the app’s code before each release. If you find a mismatch, tell us and we will fix the page or the product.
Still stuck?Chat with us, submit a ticket, or write to info@glossa.live. Most questions get an answer within the day.
© 2026 Glossa