ServiceNow MID Server 403 on Genesys Transcript Webhook

General Discussion
1

Does anyone understand why the ServiceNow MID Server rejects the Genesys Cloud webhook payload for digital channel transcript ingestion with a 403 Forbidden error? The integration functioned correctly until the recent Paris release update. Authentication tokens appear valid, and network traces confirm the MID Server receives the request. Is there a specific header or payload structure change in the latest Genesys API version causing this rejection?

2

This is actually a known issue with the Paris release tightening webhook security headers.

  1. Add X-Genesys-Webhook-Signature to the MID Server’s allowed headers.
  2. Update the ServiceNow integration script to validate the SHA-256 signature against the payload.