JSON Schema validation add more verbose error messages

We are also looking for  implementation from IBM for this solution . We are facing issue while identifying the error at the field level. It would be great if implementation to take into consideration ASAP. Thanks

Detailed JSON schema validation errors that pinpoint the exact field causing failure are essential for handling complex payloads and meeting growing business requirements.

Hi Team,

We are also looking for this solution implementation from IBM. We are also facing the similar issue while identifying the error at the field level. It would be good if implementation to take into consideration ASAP. Thanks

I support prioritizing this enhancement. Several business use cases depend on JSON schema validation, and more descriptive error messages with precise field names are critical for faster issue resolution and reduced support effort.

Hi Team,

We are looking for a solution where JSON schema validation errors include clear and specific field property names. This would greatly help users understand exactly where the validation has failed, especially when dealing with complex requests containing multiple lines of field properties.

Currently, identifying the exact issue can be challenging, and given that we’ve received multiple business requirements requesting enhanced JSON schema validation, it would be extremely valuable for users to receive more detailed and pinpointed error messages.

I strongly recommend that this change be prioritized for future enhancements.

Thank you for considering this request.

Hi Team

Even we are looking for a solution where we are expecting JSON schema validation error should contain proper field property name for users to understand where exactly this validation has failed, as its hard identify incase of multiple lines of field properties are present in coming request. please consider this for future add-ons ASAP as we have received multiple business requirements for JSON schema validation and users are expecting such validation errors in response.

I strongly vote for this change to be considered in future enhancements.

Thanks

Aswani P

Hi,

For the JSON/REST Validation, the config options should allow for verbose error responses. As of now, the response is only one "leaf" of the entire validation error tree, and with no context.

All the JSON/REST libraries I have used with are eager to dump the entire error path when validation fails. Why is this option not available in APIC?

I suggest a switch in the APIC Validation config with 3 options: [ none, minimal, verbose ] 

This allows the APIC admin team the option to be silent & secure, or verbose & helpful. Especially for test environments.

We are facing issue we do not identify the field name when validation error is occur.
i request to this enhancement 

+1 for this enhancement request at runtime. Ideally, we would like to see error payload containing the property in JSON pointer format (RFC6901) - RFC 6901 - JavaScript Object Notation (JSON) Pointer -or XPath for the case of xml content type. 

The enhancement should support both the pointer/xpath (in case of body validation error) as well as parameter (in case of query param issue).

Please support multiple errors so that users can identify all issues with the request, rathert than 1 at a time.

Hi Dan, it is normal runtime back to all clients.

Client wanted to know which element in the JSON payload failed the schema validation so they can resend the correct ones.

Thank you for opening up this request. Is this request looking for additional Schema validation output details during the

• API Designer/Testing phase

• Normal Runtime back to all clients

• Both