Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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
Created by Guest
Created on May 4, 2026

Automated Partner EDI ID Validation via API's for VAN Routing Integration

We are requesting an enhancement to enable automated validation of trading partner EDI IDs via API's against IBM VAN routing tables as part of the onboarding workflow within the IBM Sterling B2B Integration SaaS platform.

Currently, EDI ID validation and VAN routing verification require manual intervention or IBM support engagement. There is no automated mechanism to validate whether an EDI ID exists, confirm its associated VAN provider, or provision it into the appropriate interconnect mailslot.

The proposed enhancement should introduce API-driven validation with the following behavior:

  • If the EDI ID exists and matches the expected VAN provider:
    Proceed with onboarding without interruption
  • If the EDI ID does not exist:
    Automatically provision the EDI ID into the appropriate VAN interconnect mailslot and continue onboarding
  • If the EDI ID exists but is associated with a different VAN provider:
    Do not proceed with provisioning and return a structured API response indicating the mismatch, including relevant details for corrective action

The solution should also include structured API responses that clearly indicate validation outcomes, actions taken, and any errors or mismatches identified during the process. This enhancement should work in conjunction with automated API driven envelope creation enhancement that we already submitted.

  • Admin
    Manoj Panda
    May 4, 2026

    Dear Venkat,

    Thanks for submitting this idea and for clearly articulating the use cases and desired automation outcomes.After reviewing the request in the context of current VAN architecture and governance constraints, I want to clarify the scope we can support at this time.

    For the initial enhancement, we will focus on read‑only API‑based validation of trading partner EDI IDs against IBM VAN routing tables.

    In scope for this enhancement API validation to determine:Whether an EDI ID exists, Which VAN provider it is currently mapped to Structured, machine‑readable API responses indicating validation success or failure. Enable customers to make informed onboarding decisions based on deterministic, safe checks.

    Out of scope for the initial enhancement Automatic provisioning of new EDI IDs. Adding EDI IDs to VAN interconnect mailslots. Modifying or re‑routing existing VAN mappings. These actions impact shared VAN infrastructure and require additional governance and operational controls, which are not supported today via customer‑facing APIs. If the validation indicates that an EDI ID does not exist, or that there is a VAN provider mismatch, the API will surface this clearly so customers can follow existing IBM support and governance processes.We’ll proceed by updating the idea scope accordingly to reflect a safe, reusable, and productized validation capability, and we can revisit provisioning‑related automation as a separate discussion in the future. Appreciate the detailed input and continued collaboration.

    Thanks

    Manoj Panda