I’m completely stumped as to why the Genesys Cloud Bot Builder API rejects our batch training data upload. We are migrating from Zendesk Answer Bot and trying to map our historical ticket comments to Genesys intents. In Zendesk, we could simply export a CSV and import it directly into the AI training module without much fuss. The process was remarkably straightforward.
In Genesys Cloud, I am using the POST /api/v2/bots/botId/intents endpoint with a JSON payload containing the intent name and utterances. However, the API consistently returns a 400 Bad Request error. The error message is vague, citing an invalid request body structure.
{
"code": "bad.request",
"message": "Invalid request body",
"status": 400
}
I have verified the JSON syntax multiple times. The intent IDs match, and the utterances are plain text strings. Is there a specific character limit or encoding requirement for the utterances that differs from the Zendesk import format? The documentation does not explicitly state any restrictions on special characters or line breaks within the training phrases.