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 Under review
Workspace z/OS Connect
Created by Guest
Created on Mar 12, 2026

Allow (zOSConnect-3.0) Audit Interceptor to be configured at specific API level.

Currently for zOSConnect-3.0 (openAPI3), Audit Interceptor can only be configured at Global level for all Provider and Requestor APIs in the server.
This limits the ability to log API specific custom-headers to SMF, as we could only provide 4 header names to log at global level, which are not necessarily the same for all APIs.
Or atleast, the properties "apiProviderRequestHeaders", "apiProviderResponseHeaders", ... should be allowed to be configured for each API, under the webApplication configuration element.

This would then allow API specific custom headers to be logged to SMF in the same 4 fields that exist for Request/Response.

Idea priority Urgent