Platform API POST /v2/conversations returning 403 when triggered by ServiceNow MID Server

Quick question about the Genesys Cloud Platform API behavior when invoked from a ServiceNow MID Server. The integration works flawlessly via Postman but fails with HTTP 403 Forbidden when executed through the MID. The payload structure remains identical across both tests.

  • Verified OAuth2 token validity and scope permissions in the ServiceNow script include.
  • Confirmed the MID Server outbound proxy allows traffic to the Genesys Cloud tenant domain.