I can’t seem to figure out why the HTTP Request action in our Architect flow is returning a 403 Forbidden error when calling our partner API endpoint. The flow is configured to use the Genesys Cloud OAuth token for authentication, but the downstream system requires a specific client ID that is not being passed in the standard Authorization header.
The integration is built using the AppFoundry framework, and we have verified that the token is valid and active in the Genesys Cloud environment. The error occurs consistently during peak hours, suggesting a potential rate limit or scope issue with the multi-org OAuth setup. We are using the latest version of the Architect tool and have checked the API logs for any additional error details.
Has anyone encountered similar issues with custom OAuth integrations in Architect flows? We need to ensure that the correct client credentials are being used for the downstream API call without exposing sensitive information in the flow configuration.