Skip to content

RTMP ingest and stream keys

RTMP lets an encoder push your service audio straight to Glossa, with no browser open and nobody clicking Start Streaming. It suits installations that must start on their own and churches whose audio already lives in OBS, vMix or a hardware encoder. It adds a little delay compared with a direct audio input, so use a local input when you can.

Server rtmp://stream.glossa.live:1935/live
Stream key glossa_…, shown in the service’s Advanced Settings under Live Streaming (RTMP / SRT)

Only the live application is accepted. The key is tied to one service and to the speaker language it was generated for; the modal notes that the key changes with the language selection. Keys without the built-in secret are refused.

Regenerate key in the same panel invalidates every older key for that service at once. Do this if a key has leaked, then update your encoder.

  • OBS: Settings, Stream, Service Custom, Server and Stream Key from above. Start Streaming.
  • Audio is what matters. Any audio codec that an FLV/RTMP stream can carry works (AAC is typical); Glossa decodes it to 16 kHz mono internally.
  • Video is optional and is discarded on arrival. If your encoder insists on sending video, use the lowest bitrate it allows.
  • Send one encoder per key. A second publisher on the same key is refused with already has a publisher.
  1. Glossa checks the key, your balance or plan, and that no browser is already streaming the same service.
  2. The service goes live, the stream-started notifications fire, and transcription starts automatically in the language encoded in the key.
  3. Listeners pick their own languages as usual; each requested language is translated and billed per minute of speech.
  • The moment the connection closes, transcription stops and the service is off air. There is no grace period.
  • If the connection stays open but no audio arrives for 45 seconds, Glossa restarts its decoder, up to five times, then gives up.
  • RTMP streams have no session time limit. Because the stream starts by itself whenever your encoder publishes, remove Glossa as a destination when you are not using it, or a rehearsal can bill like a service.

The signed-in owner of a service can fetch and rotate its key through the same calls the app uses. They require the user’s session token and are not a public API, so treat them as internal and subject to change.

GET https://api.glossa.live/service/{SERVICE_ID}/stream-key?language=en-US
POST https://api.glossa.live/service/{SERVICE_ID}/stream-key/rotate {"language": "en-US"}

Both answer {"streamKey": "glossa_…", "language": "en-US"} with Cache-Control: no-store.

The app shows SRT Protocol (coming soon) and the button is disabled. SRT ingest is not open yet; use RTMP.

Still stuck?Chat with us on glossa.live or write to info@glossa.live. Most questions get an answer within the day.