Running a tokio loop in Rust 1.75 to fetch active calls and the latency is completely tanking the event stream. The docs list both /api/v2/conversations/calls and /api/v2/analytics/conversations/details but they’re acting weird under load. Hitting the analytics route with a standard GET drops a 403 Forbidden even though the same bearer token works fine for the real-time path. The JSON keys flip between conversationId and conversation_id too. We can’t figure out which endpoint handles the WebSocket fallback correctly.
1 Like