Why does the POST /api/v2/wfm/scheduling/scheduletemplates endpoint returns a 403 Forbidden error despite the OAuth token having the wfm:schedule:write scope?
Background
We are building a Premium App that automates shift template generation for multi-org deployments. The app uses machine-to-machine OAuth.
Issue
The request fails with a 403. The payload is valid JSON and matches the schema.
Troubleshooting
- Verified the access token is active and contains the correct scope.
- Confirmed the integration has the necessary permissions in the Developer Portal.
- Tested with a user token, which succeeds, suggesting a platform-level restriction on machine tokens.