Bot API 422 on Intent Update via Premium App

Architect & Flows
1

POST /api/v2/bots returns 422 Unprocessable Entity with message Invalid intent definition when our multi-org Premium App attempts to sync NLP models. Payload validation passes locally against the schema.

  • Verified JSON structure matches the intent object definition in Platform API v2 docs.
  • Confirmed the bot:write scope is active and the token is valid for the target org.

Any insights on hidden validation rules for custom intents?

2 
{
 "intent": {
 "name": "string",
 "description": "string"
 }
}

You might want to look at the intent object structure. The dashboard often masks validation errors related to missing description fields or duplicate names. Ensure the payload includes a non-empty description string. This discrepancy usually stems from schema differences between local testing and the production API validation rules.