Stuck on a persistent 400 Bad Request error when attempting to query real-time queue metrics via the Platform API. The organization is running on the EU-West BYOC environment, and the objective is to programmatically retrieve current queue lengths and abandoned call rates to feed into a custom executive dashboard that mirrors the standard Real-Time Performance view. The POST request is directed to the endpoint /api/v2/analytics/queue/realtime. The payload includes a standard interval object with start and end timestamps formatted as ISO 8601 strings, specifically “2023-10-27T08:00:00Z” to “2023-10-27T09:00:00Z”. The response consistently returns a 400 status code with the error message “Invalid interval: start time must be before end time”. This is perplexing because the start time is clearly earlier than the end time in UTC. The service account used for the API call possesses the Analytics Read permission and has been verified against the standard Analytics Dashboard permissions. The same time interval works perfectly when manually filtering data in the web-based Analytics dashboard, suggesting the issue lies within the API payload structure or interpretation rather than data availability. The request headers include Content-Type: application/json and the standard Authorization Bearer token. No SDK is being utilized; the call is made directly via Postman to isolate variables. The Architect flows are stable, and no recent changes have been made to the queue configurations or routing rules. The expectation is that the API should accept standard ISO 8601 formats for real-time queries without requiring millisecond precision or specific timezone offsets beyond Zulu time. Given the formal enterprise context, precision in metric retrieval is critical, and this blockage prevents automation of daily occupancy reports. Assistance in identifying the correct interval format or any hidden constraints on the real-time analytics endpoint for BYOC instances would be appreciated.