Could someone explain why the /api/v2/analytics/conversations/details/query endpoint returns a 404 when filtering for digital channel interactions? The request works for voice. I suspect a schema mismatch in the filters object for chat sessions. The payload includes standard metric definitions but fails specifically on digital types. Is there a specific permission set required for digital analytics queries?
The root of the issue is likely not a schema mismatch but rather how the query interval is handled for digital channels in the analytics api. when running load tests with jmeter, we often see 404s if the interval isn’t explicitly set to a valid bucket size like 5m or 1h. the default voice query might auto-resolve, but digital queries are stricter about time aggregation. also, check if the type filter is using chat or email specifically instead of just digital. the api docs are a bit vague on this, but in our ap-southeast-1 tests, we found that digital is an umbrella term that sometimes fails if not paired with a specific sub-channel type.
try this payload structure in your jmeter http request sampler:
{
"interval": "5m",
"view": "default",
"metrics": ["handleTime"],
"filters": {
"type": "chat"
},
"groupBy": ["direction"]
}
if you still get a 404, it might be a caching issue on the edge node. the analytics service in gc can be slow to index new digital interactions compared to voice. we noticed this when pushing 100 req/s through the outbound api; the analytics endpoint would return 404 for recent data until the batch processor caught up. add a wait sampler in jmeter to let the data settle for 15 minutes before querying. also, ensure your service account has analytics:view permissions specifically for the digital channel group. sometimes the rbac matrix is split between voice and digital permissions, causing silent 404s instead of 403s. check the admin console for role assignments.