IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Sterling REST API Update without prior get


We would like to update a specific user groups and accounts without changing the earlier configurations and permissions. In order to do so, we have to first GET the earlier configuration of the interested account, then add the new configuration on top of the JSON and then run an UPDATE call. We do not want to run the GET call first to be able to update without removing earlier configurations. Just a JSON/XML script containing just the new configurations should be enough.

In another words, we would like to see an ADD call in addition to UPDATE/PATCH.


Thanks and kind regards,


  • Guest
  • Apr 4 2018
  • Planned for future release
What is your industry? Banking
How will this idea be used?

We would like to automatize our user and group permissioning schemes

  • Guest commented
    27 Feb, 2020 09:56am

    adding ADD calls to Several of the other API calls would be quite useful and streamline many processes

  • Admin
    Ryan Wood commented
    11 Feb, 2020 02:01pm

    Hello, we have further analyzed this issue and have accepted this to our roadmap. All roadmap items we strive to deliver withn 12 months. Thank you.

  • Guest commented
    9 Dec, 2019 12:44pm



    In user account update API, you can either update all the information with default update function, or you can use partial update to update only permissions. In either case, when you make an API request with single(or multiple) permissions passed in the json data, the earlier permissions are overriden by the new permissions you push. We would like to be able to add permissions to a user without deleting the earlier ones. (As a workaround, we are running read API for that user, collect all the permission it currently has, append the new permission we want to assign to json data, and push it back for that user.)




  • Admin
    Ryan Wood commented
    5 Sep, 2019 02:11pm

    Thank you for participating in the request for enhancement community. We have evaluated this request, and would like to request some additional information.

    Can you provide some additional details on the use case?

    Can you provide sample GET and UPDATE API calls?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.