Just noticed that bulk export jobs for chat interactions routed via Predictive Routing fail with HTTP 403. The S3 destination is correct, and the service account has recording:export and digital:read permissions. The error occurs only when the routing_strategy is set to predictive. Standard queue routing exports fine. Is there a specific permission for predictive metadata? See Genesys Docs.
GET /api/v2/quality/evaluations
Headers: Authorization: Bearer {token}
You need to add the quality:evaluation:read permission to the service account. The 403 occurs because predictive routing exports pull evaluation metadata. Standard permissions cover recordings, not quality data. AppFoundry deployments often miss this scope during initial OAuth setup.