Platform API 400 on Queue Settings payload validation

Hi all. ADMIN UI is preferred but timing out on bulk changes, forcing PLATFORM API usage for QUEUE SETTINGS. Payload rejects WRAP_UP_TIME and SKILLS arrays with 400 error on US-EAST cluster using PYTHON SDK 12.0.4. Stripped payload to QUEUE_ID and ACD_SETTINGS, but SKILLS object still flagged malformed; API schema seems stricter on nested ROUTING RULES than ADMIN UI. ARCHITECT FLOW not triggered, just settings sync. CONSOLE LOGS show raw 400 dump. Replaced skill IDs with directory UUIDs, same rejection.

Updating queue settings
{
 "error": "invalid_request",
 "message": "Validation failed: skills[0].id must be a valid skill identifier",
 "status": 400,
 "code": "bad_request"
}
1 Like