Can anyone clarify why PATCH /api/v2/outbound/campaigns/{id} returns a 400 Bad Request when updating the dialer_settings for a predictive campaign? The payload validates fine in the sandbox, but production rejects it with invalid_dialer_configuration. Here is the exact payload being sent:
{
"dialer_settings": {
"campaign_type": "predictive",
"max_abandon_rate_pct": 2,
"max_agent_hold_time_sec": 30,
"dial_ratio": 3.5
}
}
You need to align the API payload structure with the strict validation rules enforced by the Outbound platform for predictive campaigns. The error invalid_dialer_configuration typically occurs when the JSON structure omits mandatory nested objects or contains conflicting parameter values that violate business logic constraints.
Cause: The platform’s predictive dialer engine requires specific configuration blocks to be present and logically consistent. When campaign_type is set to predictive, the system expects explicit definitions for pacing logic and agent interaction limits. The error often arises from missing the strategy object or providing a max_abandon_rate_pct that conflicts with the configured strategy parameters. Additionally, timezone mismatches in timestamp fields within the payload can trigger validation failures in production environments, even if they pass sandbox checks.
Solution: Restructure the dialer_settings object to include all required nested fields. Ensure the strategy object is explicitly defined with valid pacing parameters. Below is a corrected payload structure:
{
"dialer_settings": {
"campaign_type": "predictive",
"max_abandon_rate_pct": 2,
"max_agent_hold_time_sec": 30,
"strategy": {
"strategy_type": "predictive",
"max_calls_per_agent_per_hour": 60,
"target_abandon_rate_pct": 2
},
"flow_id": "your_flow_id_here"
}
}
Verify that the flow_id corresponds to an active outbound flow. Check the platform logs for detailed validation errors if the issue persists. Adjusting the target_abandon_rate_pct to match max_abandon_rate_pct often resolves configuration conflicts.