Encountering a 403 Forbidden error when invoking the /api/v2/interactions/screen-recordings endpoint for calls routed through our Singapore BYOC trunks. The Architect flow successfully initiates the recording, and the UI shows the red indicator, but the subsequent API call to retrieve or list the recording fails with an access denied response. This occurs specifically for interactions associated with trunks configured under the APAC region, while standard PSTN calls in the same flow record and retrieve without issue.
The tenant ID matches the trunk ownership, and the OAuth token possesses the required screen-recording:read scopes. Verified that the interaction UUIDs are correct by cross-referencing the call logs. The discrepancy suggests a potential mismatch in how BYOC trunks tag recording metadata or permissions compared to native Genesys Cloud trunks. Has anyone observed similar scope limitations or regional restrictions when attempting to access screen recordings for BYOC-initiated interactions via the API?