What is the reason the /api/v2/bots/{botId}/intents endpoint is rejecting our payload with a 400 Bad Request when we try to map Zendesk macro tags to Genesys Cloud intents via the migration script? The payload structure looks valid according to the docs, but the response body returns a generic validation error without pointing to a specific field. We are using the Genesys Cloud SDK v10.12.0 for Python and have verified the bot ID exists and is active in the eu-west-1 region. The intent names are alphanumeric and under 255 characters, so length shouldn’t be the issue. In Zendesk, macro tags were just simple string identifiers, but Genesys Cloud seems to require a more complex structure with utterances and entities right at creation time. We are trying to automate this mapping to save time on manual configuration, but the API seems to be enforcing strict validation that isn’t clearly documented for bulk operations. The error occurs immediately upon POST request, before any training data is added. We have checked the request headers and authentication tokens are valid, as other API calls in the same script succeed. The timezone setting in the bot is set to Europe/Paris, matching our user accounts, so that shouldn’t cause a conflict. We are migrating about 200 macros and have successfully imported the first 50, so the issue might be related to specific characters in the macro names or a rate limit we are hitting. The script logs show the exact JSON being sent, and it matches the example in the developer guide. We are considering adding a delay between requests, but the error happens on the first request of each batch. How can we properly format the intent creation payload to avoid this 400 error during bulk migration from Zendesk?