Does anyone understand why the PUT /api/v2/conversations/cobrowsesessions/{conversationId}/recordingstate endpoint returns a 403 Forbidden error with the message Insufficient permissions to update recording state? Our AppFoundry integration uses a valid OAuth2 client credentials flow with the recording:write scope explicitly granted in the Genesys Cloud admin portal. The token is fresh and valid for other read operations like /api/v2/users/me.
We are building a custom playback interface that requires initiating server-side recording triggers. The documentation states that recording:write is sufficient for session management. However, the 403 response suggests a deeper permission hierarchy or a missing role assignment on the OAuth client itself.
We have verified that the associated user role has ‘Manage Recordings’ enabled. This issue is blocking our Q3 release for a major enterprise client. Is there an additional hidden scope or a specific API gateway policy in the us-east-1 region that restricts state updates for partner integrations? We need a workaround or a confirmation if this is a known regression in the latest patch.