Docs state: “The /api/v2/analytics/conversations/details/query endpoint is designed for reporting and historical data retrieval.” I’m getting a 204 No Content on the analytics call while the direct conversation endpoint returns 200 with the full object. This seems backwards for a simple lookup.
I’m using the Python SDK. Here is the call that fails:
response = analytics_api.post_analytics_conversations_details_query(
body=AnalyticsQueryBody(interval="2023-10-01T00:00:00Z/2023-10-02T00:00:00Z", pageSize=1, query="conversationId:12345678-1234-1234-1234-123456789012")
)
The response is empty. Status 204. No headers indicating why.
If I switch to the conversations API:
response = conversations_api.get_conversation(conversation_id="12345678-1234-1234-1234-123456789012")
It works instantly. Returns the JSON payload.
I need the analytics endpoint because I need the wrap-up code and disposition fields which aren’t always populated in the real-time conversation object. The docs don’t mention a delay or a specific query format requirement for single ID lookups in analytics. Is the interval parameter required even if I’m filtering by ID? Or is this a caching issue?