Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Workspace API Connect
Created by Guest
Created on Dec 12, 2023

JSON Schema validation add more verbose error messages

When a schema validation error occurred, it would be good for API Connect to output either the field name or the line in the request that it failed on. This will assist the client greatly at finding out which field actually failed the schema validation.

Idea priority High
  • Guest
    May 30, 2025

    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.

  • Guest
    May 1, 2025

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

  • Guest
    Apr 28, 2025

    +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.

  • Guest
    Mar 11, 2024

    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.

  • Guest
    Mar 8, 2024

    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