Looking for advice on a specific authorization failure when attempting to pull granular bot interaction metrics for calls routed through our 15 BYOC trunks. We are using the Genesys Cloud API v2 endpoint /api/v2/analytics/conversations/details/query with a POST payload filtering for bot type interactions. The request succeeds for standard SIP trunks but consistently returns a 403 Forbidden response when the routing filter includes our BYOC carrier IDs.
The delegated user assigned to the API integration has the Administrator role and explicit analytics:read scope. The tenant is configured with strict data residency policies, routing traffic through our Singapore edge node. I have verified that the SIP registration status for all BYOC trunks is Registered and failover logic is functioning correctly based on the 487 termination logs we monitored earlier this week. The issue appears isolated to the analytics pipeline’s ability to associate bot session data with the specific carrier trunk identifier during the export process.
Has anyone encountered similar scope restrictions where BYOC trunk metadata is treated differently than standard Cloud trunks within the analytics engine? How can we resolve the 403 error when querying bot conversation details for specific BYOC trunk IDs?