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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories Usability
Created by Guest
Created on Jan 13, 2021

Make FGArrivedFile REST API useable.

A great use for the Sterling REST API would be to query the FGArrivedFile, FGRoute, and FGDelivery endpoints in order to build a modern delivery dashboard for business users.
This is currently impossible with the current implementation due to a couple of poor implementation choices.

1. the ModifyTs cannot be queried on, thus making it impossible to query for recently changed entries.

2. Having to query all 3, FGArrivedFile, FGRoute, and FGDelivery and merging the data between the arrivedFileKey and RouteKey is a usability nightmare. All of the data is relevant and must be combined into 1 endpoint.

3. Once the above is completed then the REST API will finally be somewhat usable; however, not modern. A modern implementation would allow consumers to subscribe to changes via websocket so that consumers could get instant updates to transmissions without having to constantly poll the rest api.

1&2 is a must. 3 is a nice to have.

What is your industry? Financial Markets
How will this idea be used?

This will allow us to continue to build out our managed file transfer program and deliver to the business visibility and self service features. IBM continues to reaffirm that users of Sterling should build solutions for the business outside of Sterling instead of inside. This is due to the fact that we still do not have granular permissions and the user interface continues to lack usability for non-tech business users.