HTTP 400 Bad Request on POST /api/v2/dialog/update returns {"error": "invalid_slot_mapping"} when the Java webhook pushes spaCy NER results back to Cognigy. The context-aware disambiguation routine strips the ambiguous PERSON tag and tries to assign dialogState.slots["customer_name"] = extractedEntity.value; but the REST call keeps bombing out. Doesn’t look like the raw utterance history is serializing right for multi-turn continuity anyway.
{
"dialogId": "gen-123",
"slots": { "customer_name": { "value": extractedEntity.value } }
}
Tried direct assignment, failed. Don’t wrap it in platformClient.DialogsApi.updateDialog, it still bombs on history serialization. Logs show 400s everywhere. The payload expects explicit interactionId routing. What schema version is your webhook actually targeting?