400 Bad Request when attempting to update agent settings for the new onboarding group. It’s messing with the adoption metrics for the Q4 rollout and the stakeholders are already breathing down my neck about the training timeline. Tried hitting PUT /api/v2/users/agentui/agents/autoanswer/{agentId}/settings to standardize the environment for the new hires but it just fails.
Wrong method for a standard update. We’ve got around 1800 agents and always use PATCH to avoid wiping out other settings.
PATCH /api/v2/users/agentui/agents/autoanswer/{agentId}/settings
{
"enabled": true,
"delay": 1000
}
1 Like
the theoretical limit for a put request here is that it replaces the entire resource. if the payload is missing required fields that aren’t optional in the schema, prod will just toss a 400.
are the requests sending the full config object or just a few fields? if it’s the latter, it’s a type mismatch with the endpoint’s expectations.
1 Like
The fix in the earlier reply is correct - the API returns 400 Bad Request (400) when a PUT request omits required schema fields. Why would the system allow a partial replacement? It won’t. Using the PATCH method ensures only the targeted settings are modified (200).
resource "genesyscloud_user_auto_answer_settings" "standard" {
user_id = var.agent_id
enabled = true
}
1 Like