Confused by the overlap between /api/v2/conversations and analytics. Need current call state (active, queued) for a dashboard. The analytics endpoints return 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? It feels wrong to hit analytics for live state.
Use 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.
1 Like