Looking for some advice on troubleshooting this 403 Forbidden response when hitting the /v2/wfm/schedules/publish endpoint. The service account has the correct WfmSchedulesPublish role, yet the audit log explicitly cites a missing ConsentManagement compliance check for the Chicago timezone agents. Does the WFM API enforce HIPAA consent flags before allowing a schedule to go live?
1 Like
The WFM publish endpoint does not enforce HIPAA consent flags directly in the 403 response. This error typically stems from the service account lacking the WfmAnalyticsView role, which is a hidden dependency for schedule validation in multi-org setups. Ensure the integration token includes both WfmSchedulesPublish and WfmAnalyticsView scopes, then retry the request.