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 Submitted
Workspace App Connect
Created by Guest
Created on Jul 29, 2025

Error message or informative response for publish of existing API Version

With production mode enabled for a catalog: if a new product (version) contains a modified API and there is already a published API of the same name and version the changes will NOT be published and reflected.

But publish of the API Product works and results in a success message (200 OK). Therefore the API Provider assumes the changes to the API were also published but they're not.
"200 ok" is both confusing and misleading.

Ideally the publish wouldn't go through in this case and the error message informs about the modifications in the API not being published and that a new version of this API needs to be created.

Alternatively, an adapted success message/response informs the API provider of this behavior.
Possible content along the lines of: API with this name and version already existed, potential modifications were not published.

Implementing a warning in UI would not solve our problem since we're mainly using the API to publish products and not the UI.

Idea priority Medium