GET /api/v2/analytics/conversations/details returns a 404 Not Found when filtering by custom digital channel metrics in the last 24 hours. The standard voice metrics populate correctly, but the JSON response excludes the digital object entirely.
The ServiceNow integration relies on these specific fields for ticket prioritization. Is there a known lag in the analytics pipeline for webchat and messenger data, or does the interval parameter need adjustment for real-time digital channel reporting?
My usual workaround is to checking the interval parameter. The API requires ISO 8601 duration format like P1D for 24 hours. Using 24h often causes parsing errors that return empty results or 404s. Also, digital channel analytics have a 15-30 minute propagation delay. Verify the start time is at least 30 minutes in the past.
The best way to fix this is… to ensure the interval is strictly ISO 8601. I switched from 24h to P1D in my JMeter config, and the digital metrics finally appeared.
Also, keep an eye on the propagation delay. Digital channels lag behind voice, so querying for data less than 30 minutes old often returns empty sets or 404s.
The simplest way to resolve this is to validate the ISO 8601 interval format. Digital channel metrics often lag behind voice data, so ensure the query window accounts for that propagation delay.
| Parameter |
Requirement |
| Interval |
Strict ISO 8601 (e.g. P1D) |
| Data Age |
>30 minutes |
Check your request payload structure next.