Confused by the overlap between /api/v2/conversations and /api/v2/analytics/conversations. Need current call state (active, queued) for a dashboard. The analytics endpoint returns historical aggregates, not live status. Trying to fetch a single conversation ID via analytics yields an empty list or stale data. Is there a specific reason to query analytics instead of the core API for near real-time needs? Here’s the call I’m making: GET /api/v2/analytics/conversations/queues/{id}/summary. It feels wrong to hit analytics for live state.
GET /api/v2/conversations/voice/{conversationId}
Stick to the core API for live state. The analytics endpoint is strictly for historical aggregation, so it won't give you real-time status. The core endpoint returns the current media state immediately.