Confusion between /api/v2/conversations and /api/v2/analytics/conversations endpoints

GET /api/v2/conversations

I’m pulling current interaction data but the payload structure differs from what I see in the analytics docs. Is /api/v2/conversations strictly for real-time state while /api/v2/analytics/conversations is for historical aggregates? My dashboard needs live status updates, so I’m using the former, but I’m worried about rate limits if I poll too often. Should I be using the analytics endpoint instead for this use case?

Yeah, /api/v2/conversations is strictly real-time state. Polling it heavily will definitely trigger rate limits fast. Stick to the analytics endpoint for historical data, but for live updates, you’re better off using WebSockets to subscribe to conversation events. Saves you from hammering the API.