Encountering consistent HTTP 400 Bad Request errors when querying the /api/v2/analytics/interactions/summary endpoint for our AP-1 BYOC trunks. The request payload includes standard filters for timeRange and segment targeting specific trunk IDs. The error response body indicates a validation failure on the segment parameter, specifically citing an invalid operator for the trunkId field.
This setup works perfectly for US1 and EU1 regions, suggesting a regional quirk or a recent schema change in AP-1. The SDK version is 2.45.0. Has anyone else seen this behavior when filtering by BYOC trunk identifiers in the Singapore region? The documentation suggests EQUALS should be valid, but the API rejects it with a 400.
Curious if there is a known issue with how AP-1 parses the segment logic for trunk metadata, or if the trunk IDs need to be formatted differently for the analytics engine in this region. The standard trunkId value pulled from the provisioning dashboard seems correct. Any insights on the correct operator or parameter structure for AP-1 trunk filtering would be appreciated. Need to finalize the carrier failover report by end of day.