Outbound Campaign fails to initialize with 400 Bad Request

General Discussion
1

Has anyone figured out why the Genesys Cloud Outbound API returns a 400 error when trying to replicate Zendesk’s auto-assignment logic? We are migrating our outbound workflows and hitting a wall with the campaign configuration.

  1. Created a new campaign via the /api/v2/outbound/campaigns endpoint.
  2. Mapped the Zendesk ticket fields to the required Genesys Cloud attributes.
  3. Attempted to start the campaign, but the system rejects the payload with an invalid field error.

The documentation is vague on the exact schema requirements for custom attributes in this context.