deepgram-websocket
deepgram-websocket
Get Active Streams
Changed onGet information about active audio streams (from Redis) and the Deepgram connection tracker (registered slots vs cap — includes any leaked slots, so tracker.active >> local_sessions means the slot leak is accumulating).
Admin only (2026-09-18 route-auth review). Session ids here are deepgram_{callId}_{userId}_{lang}_{ts}, so this list names who is in which room, alongside the per-session billable seconds; test_every_route_answers.py had it in its "worth a look" list as "ops telemetry with no auth". The loadtest and monitoring scripts under e2e/loadtest that read it now need an admin token.
get/ws/deepgram/active-streams
Request
- Base URLhttps://api.fluentea.com (the document declares no server; this is the origin it was published from)
- URLhttps://api.fluentea.com/ws/deepgram/active-streams
- Authnone declared
Headers
authorizationstring nullable
Response
Successful Response
unknown required
Changes
- info
added the new optional
headerrequest parameterauthorization - info
added the non-success response with the status
- info