Context:
Our AppFoundry integration manages screen recording configurations for enterprise clients across multiple Genesys Cloud organizations. The application uses multi-org OAuth tokens to provision and manage recording settings. Recently, calls to POST /api/v2/screen-recording/configurations are failing with a 401 Unauthorized error. The token is valid for the target organization, as verified by successful calls to GET /api/v2/users/me. The error occurs immediately after token acquisition. The integration uses the standard Platform API client library version 2.15.0. No changes were made to the OAuth scopes or application permissions in the Partner Portal. The issue affects all new organizations added to the federation but persists for existing ones after token refresh.
Question:
Does anyone know if there is a specific scope requirement for screen recording API access that differs from standard user management? We have screen-recording:write and screen-recording:read enabled. Is there a known latency issue with permission propagation in multi-org setups, or could this be related to the recent API gateway updates? The request headers include the correct Authorization: Bearer token and Content-Type: application/json.