Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Functionality already exists
Workspace z/OS Connect
Created by Guest
Created on Jan 17, 2022

Add the support of required field in APIS Body

We need to force APIs consummer to provide mandatory fields in the JSON body of an APIS.
This is really important for APIS that use a MQ service because in this case we have no way to check fields before the message is PUT in the queue by the service.
This option is available in swagger 2.0 specification : https://swagger.io/specification/v2/ we can use things like this :

"definitions": {
"ErrorModel": {
"type": "object",
"required": [
"message",
"code"
],
"properties": {
"message": {
"type": "string"
},
"code": {
"type": "integer",
"minimum": 100,
"maximum": 600
}
}
}

But in the APIToolkit we cannot set anywhere this options in request mapping.
Of course we can use query/path parameter where this option is avaiblable but we cannot put all the fields as path/query paramters.

Idea priority Urgent
  • Admin
    Demelza Farrer
    Dec 3, 2025

    This IDEA has been assessed by the team.
    Whilst, within the zosConnect-2.0 feature that supports OpenAPI 2 we don't have that capability. Within the service there is no mechanism to mark fields as required and so the JSON schema lists every field as optional. We do have this in the zosConnect-3.0 feature that supports OpenAPI 3 already and will over the course of 2026 support OpenAPI 3. There isn't any specific documentation on it as it is just a case of using the required keyword within the Open API document where fields are required.

    As such this IDEA is being closed as delivered.
    If you have any further requirements in addition to the capability that exists today, we would welcome another IDEA

  • Guest
    Jun 23, 2022

    Hello,

    You are redirecting to a RFE that is no more under consideration & that has not been resubmited. Is there another RFE on the same subject or do i need to resubmit it again ?

  • Guest
    Jan 24, 2022

    Thank you for this RFE.

    We are accepting this requirement to cover the need for z/OS Connect to be able to host APIs that have schema with mandatory fields described in the OpenAPI specification of the API. If you require validation that mandatory fields are provided on requests to, for example, reject requests without those fields, then please vote on accepted RFE 147569, which covers the need for API request validation:
    http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=147569