Configuration is broken for some reason… We are migrating outbound lists from Zendesk to Genesys Cloud v2.0. The campaign fails with a 400 Bad Request on /api/v2/outbound/campaigns. In Zendesk, we just uploaded CSVs directly. Here, the JSON schema validation rejects our contact_uri format. How does GC expect the phone number structure compared to Zendesk’s simple string field? Need a quick fix.
If I remember correctly, Genesys Cloud requires E.164 formatting for contact_uri. Zendesk’s loose string format won’t pass schema validation. You need to prefix every number with + and include the full country code.
Try updating your CSV parser in JMeter to enforce this. Add a tel: prefix if the API docs for that specific endpoint require it, but standard +65XXXXXXXX usually works for outbound.
Check the contacts array structure too. It often needs a specific phone_number object nested inside, not just a flat string. The 400 error usually points to missing fields in that JSON hierarchy.
The documentation actually says E.164 is mandatory, but the schema often fails on metadata mismatches rather than formatting.
Instead of fixing the CSV parser, map the Zendesk fields to Genesys Cloud contact attributes via a Data Action. This ensures the contact_uri is sanitized server-side before the API call, bypassing client-side validation errors entirely.