MuleSoft · JSON Module
JSON:SCHEMA_NOT_HONOURED
Short answer
JSON:SCHEMA_NOT_HONOURED means the JSON Module's Validate schema operation found that the document does not match its JSON schema. The error description holds a JSON array with one object per validation error, so read it to see which fields failed.
VerifiedLast verified
01Error text
Error type: JSON:SCHEMA_NOT_HONOURED02Likely causes
- Validation failed because the input does not adhere to its schema.
- Example messages are
object has missing required properties (["b"])andstring "" is too short (length: 0, required minimum: 1).
03How to fix it
- Read the error description. It contains a JSON array with one object for each validation error.
- Correct the document, or the schema if it is stricter than intended.
- Handle the failure with an error handler of type
JSON:SCHEMA_NOT_HONOURED.
iNotes
JSON Schema Drafts 3 and 4 return a different payload shape from later drafts.
04Official documentation
→Related errors
- 400 Bad Request from the JSON Threat Protection policyAn API protected by the JSON Threat Protection policy returns 400 Bad Request when the JSON body exceeds one of the limits set in the policy. Send a smaller or shallower body, or raise the limit that legitimate requests hit.
- APIKIT:BAD_REQUESTAPIKIT:BAD_REQUEST is the APIkit for REST error type that maps to HTTP status 400 with the response message "Bad request". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
- VALIDATION:MULTIPLEVALIDATION:MULTIPLE is the single error the Validation module's All and Any scopes raise to summarize the validations that failed inside them. Read the error description to see which validations failed, then fix those values.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer