Stuck on a 400 Bad Request when injecting carrier failover metadata into WFM shift templates via the /v2/wfm/schedules endpoint. The payload structure mirrors our successful Architect flow implementations, yet the validation fails silently without specific field errors.
Background
Managing 15 BYOC trunks across APAC requires precise alignment between telephony capacity and WFM scheduling. We are attempting to push custom SIP registration status tags to the WFM API to optimize agent availability.
Issue
The request returns HTTP 400 immediately. No detailed error object is returned in the response body, only a generic failure message. This occurs consistently across all three regions.
Troubleshooting
- Verified API token permissions include
wfm:schedule:write. - Confirmed JSON schema validity using external validators.
- Tested against a non-BYOC trunk configuration, which succeeded.