Looking for advice on a persistent 401 Unauthorized error when attempting to inject a WebRTC agent session token into a ServiceNow variable via a Data Action. The environment is running Genesys Cloud Release 2024.3, and the ServiceNow instance is Washington DC. The Architect flow successfully retrieves the agent.session.token from the GET /api/v2/fleet/agents/{agentId}/session endpoint, but the subsequent POST to /api/now/table/u_webrtc_ticket fails validation. The payload includes the token as a string, yet ServiceNow returns a generic authentication failure despite the OAuth2 client credentials being valid for standard API calls. Cross-referencing the documentation suggests the token format should be base64 encoded, but the raw JSON output from the Genesys API appears correct. Is there a specific header requirement or payload structure adjustment needed when passing WebRTC tokens to external REST endpoints? The error logs show the request reaches ServiceNow, but the u_webrtc_token field triggers a script include failure. Any insights on handling these tokens in Data Actions would be appreciated.