Looking for advice on why 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 multi-org AppFoundry integration that pushes script updates programmatically via the API. The integration uses a service account with the following scopes: wfm:schedule:write, wfm:assignment:write, and routing:campaign:write. The initial authentication succeeds, and we can retrieve existing schedule templates using GET /api/v2/wfm/scheduling/scheduletemplates without issue. However, when attempting to create a new template, the API consistently returns a 403.
Environment
- Genesys Cloud Version: Latest stable (as of Pacific Time, 10/24/2023)
- SDK: Python
genesyscloudv2.0.1 - Integration Type: Multi-tenant AppFoundry partner application
Request Details
POST /api/v2/wfm/scheduling/scheduletemplates
Content-Type: application/json
Authorization: Bearer <valid_token_with_wfm:schedule:write>
{
"name": "Template_Auto_Gen",
"description": "Automatically generated template for high-volume shifts",
"scheduleGroups": [
{
"name": "Default Group",
"assignments": []
}
]
}
Error Response
{
"code": "forbidden",
"message": "User does not have permission to perform this operation.",
"status": 403
}
We have verified that the service account has the correct permissions assigned in the Admin UI. The error persists even when using a fresh token. Is there a hidden dependency or additional scope required for template creation that is not documented in the standard WFM API reference? This is blocking our deployment to production for three major clients.