How come this setting causes the POST /api/v2/conversations/messages/agentless endpoint to return a 403 Forbidden error when using a multi-org OAuth token, even though integration:all scope is granted? Our AppFoundry partner integration handles high-volume outbound messaging, and the failure occurs specifically when the target user is in a different organization than the token issuer. Environment: Node.js v18, Genesys Cloud API v2. Error: 403 Forbidden - Insufficient permissions for cross-org interaction creation.
1 Like