Outbound Campaign API 400 Bad Request on 'dialingPolicy' field

POST to /api/v2/outbound/campaigns returning 400 Bad Request when dialingPolicy is set to PREDICTIVE without powerLevel explicitly defined in the payload. The documentation implies defaults should apply for new campaigns, yet the validation layer rejects the request with: “The property ‘powerLevel’ is required for dialingPolicy ‘PREDICTIVE’.”

Our integration handles multi-org provisioning, so we cannot hardcode power levels per tenant. We are attempting to leverage the platform’s default behavior to simplify our Terraform state management. Is this a strict requirement for all API-driven campaign creations, or is there a specific header or feature flag enabling default inheritance?

Testing against the US-East region, API version 2024-01-15. This behavior disrupts our automated rollout scripts for new client onboarding. Any insights on bypassing this validation or correctly structuring the JSON body to inherit defaults would be appreciated.

Default powerLevel is 1. Add it to the JSON payload.

"dialingPolicy": "PREDICTIVE",
"powerLevel": 1