What is the reason the WFM API endpoint /api/v2/wfm/schedules returns a 403 Forbidden error when invoked from our ServiceNow integration script?
The OAuth token is generated via the standard client credentials flow and has been verified to have the wfm:schedule:write scope. The request payload matches the v2 documentation structure exactly, including the required scheduleId, agentId, and shift definitions. We are running this from a London-based instance (eu-01) and have confirmed that the ServiceNow instance IP is whitelisted in the Genesys Cloud firewall settings. The error response body is empty, providing no further details on the specific permission failure. Other endpoints like /api/v2/wfm/forecasting work correctly with the same token, suggesting the issue is isolated to the schedule creation/update functionality. We have attempted rotating the API credentials and verifying the user permissions in the Genesys Cloud admin console, but the 403 persists. Is there a specific role requirement or API key restriction for bulk schedule operations that might be causing this?