Trying to initiate a call via the REST API but getting a 400 Bad Request. The docs say the participant address needs to be a valid tel URI, but I’m not sure if I’m formatting it right. Here’s the payload I’m sending:
{
"to": [{"address": "tel:+15550199", "name": "Test"}],
"from": {"address": "tel:+15550100"}
}
Getting "message":"Invalid participant address". Am I missing a scheme or is the phone number format wrong?
The issue is likely the missing scheme in your to array. The docs are pretty specific about this. From the Genesys Cloud API documentation for POST /api/v2/conversations/calls:
“The address must be a valid tel URI. For example: tel:+15551234567.”
You have tel:+15550199 which looks correct at a glance, but sometimes the SDK or raw HTTP client strips or mangles the scheme if not explicitly typed. In C#, if you’re using the PureCloudPlatformClientV2 SDK, make sure you’re creating the ConversationCall object correctly.
Try this:
var callRequest = new ConversationCall
{
From = new ParticipantAddress
{
Address = "tel:+15550100",
Name = "Outbound Caller"
},
To = new List<ParticipantAddress>
{
new ParticipantAddress
{
Address = "tel:+15550199",
Name = "Test Recipient"
}
}
};
var response = await platformClient.ConversationsApi.PostConversationsCallsAsync(callRequest);
If you’re hitting the API directly with HttpClient, ensure your JSON is serialized exactly as shown. A common mistake is sending "address": "+15550199" without the tel: prefix. The API is strict on this. It’s not just a phone number, it’s a URI.
Also, check your OAuth scopes. You need conversation:write and routing:interaction:write. Missing a scope usually gives a 403, but sometimes the validation fails early with a 400 if the token isn’t fully valid for the action.
Another thing to check is if the from number is a valid outbound caller ID in your organization. If it’s not configured in Admin > Outbound Call Settings, the API might reject it. But the error message points to address format, so stick to the tel: scheme first.
Don’t forget to handle the async call properly. If you’re using Azure Functions, make sure you’re not blocking the thread. Use await all the way down.
The SDK handles most of the serialization, so if you’re still getting the 400, try logging the raw request body before it goes out. Sometimes the serializer drops the tel: if the type is inferred wrong.
Check your browser console or Postman to see the exact error details. The message might have more info in the details array.