Stuck on a persistent 400 Bad Request when updating entity mappings via the Bot Builder API.
We are developing a multi-tenant integration that dynamically updates bot intents based on client-specific data sources. The issue arises when calling PUT /api/v2/bots/{botId}/languages/{languageId}/intents/{intentId}. The payload includes updated entity synonyms and mapping rules, which are validated locally against the schema. However, the API consistently returns a 400 error with the message “Invalid entity reference in intent definition.” This occurs specifically when the entity is linked to an external knowledge base connector rather than a static list. The environment uses the latest Genesys Cloud SDK for Python (v2.8.4) and the bot is deployed in a production org with strict API rate limiting. We have verified that the entity ID exists and is accessible via the GET /api/v2/bots/{botId}/languages/{languageId}/entities endpoint. The request headers include the correct OAuth2 bearer token and content-type. Interestingly, manual updates through the Genesys Cloud UI succeed without error, suggesting a discrepancy in how the API validates external entity references compared to the UI logic. Has anyone encountered similar validation issues when programmatically managing dynamic entity mappings in a Premium App context? We need a reliable way to automate these updates without triggering validation failures.