PATCH-role API not working to change roles en masse

[jared-fox]

I have about 130 roles I wish to add an entitlement to. They all have a common term in their name, so I used a powershell script to filter out all the appropriate roles and their ID numbers.
After that, my plan was to use the PATCH role Beta API call (patch-role | SailPoint Developer Community) to add the entitlement. I wanted to test in sandbox first so I attempted it with 3 role ID’s, and upon failing with 1 role ID, which failed again.

I believe my Params were correct:

I assume my mistake is somewhere in the JSON where I am attempting to define the addition of the entitlement:

I am trying to carefully follow the documentation, but I feel like this must be where I am messing up, unless there is something else I am missing.

Here is the JSON in text incase you wish to copy and paste to evaluate: [

  {
    "op": "add",
    "path": "/ENTITLEMENTS",
    "value": "New entitlement"
  },
  {
    "entitlements": [
      {
        "id": "42b76fd73fd74badb9549717a2cb0637",
        "type": "ENTITLEMENT",
        "name": "GROUP - Group Sales"
      }
    ]
  }
]

Any help would be appreciated as I am not looking forward to doing large manual edits like this if it can be avoided.

[santupatel2025 (Santosh Patel)]

Hello Jared,
Please follow below screenshot and adjust your request body.

Please let me know.
Santosh

[santupatel2025 (Santosh Patel)]

Also try updating one entitlement for a single role first to check if it works.

[jared-fox]

Hi Santosh,
I edited the JSON to reflect what you sent me but I got the same response:

I also reduced the numbers of roles I’m requesting change for like you suggested:

I made sure all the entitlements and roles involves are enabled. Are there any other configurations for the roles and entitlement I need ot worry about?

[suresh4iam (Suresh Kumar Palanisamy)]

Hey,
Can you check the below configurations in your PATCH operation?

Headers:
Content-Type: application/json-patch+json

Body:

[
  {
    "op": "add",
    "path": "/entitlements/-",
    "value": {
      "id": "63b09cba8bce4f079b3a1b3f00b32bc23",
      "type": "ENTITLEMENT"
    }
  },
  {
    "op": "add",
    "path": "/entitlements/-",
    "value": {
      "id": "9a9e9946d79344388884f26763ce2qc4",
      "type": "ENTITLEMENT"
    }
  }
]

[jared-fox]

Hi Suresh,
I was able to add the “Content-Type application/json-patch+json” to my headers and now the call appears to return a 200 OK code, but when I check the role the entitlement does not appear to have been added.

Where was I supposed to add the body change you suggested:

I am only adding one entitlement to these roles, here is my current body below:

I feel like we’re getting close, thank you for your help!

[santupatel2025 (Santosh Patel)]

Hello Jared,

It did work for single entitlement?
Are you trying to add same entitlement to 3 different roles?

Thanks,
Santosh

[suresh4iam (Suresh Kumar Palanisamy)]

I can see the entitlement got added in your response. But not sure whether that is something added earlier.

Can you double check whether the Role name and the entitlements added are matching?

Are you trying to add an entitlement to multiple Roles in a single PATCH call?

[jared-fox]

That is the current entitlement associated with that role. It did not add the new entitlement:

[jared-fox]

It did not work for a single entitlement. It is showing 200 OK but the new entitlement hasn’t been added for some reason.

[jared-fox]

I accidentally copied in the Source ID from the entitlements json object…I’m stupid. I didn’t realize the entitlement ID was at the bottom. It appears to be working now. I’ve only tested with one role though.

[suresh4iam (Suresh Kumar Palanisamy)]

I doubt it earlier hence asked you to double check the Role and entitlement details. Glad it works for you.

[jared-fox]

Thanks so much. I appear to have hit another issue though. I am using “Bulk Edits” in the path variables (Params) fields to input the roles I want to edit, but it’s only editing the last listed role:

Am I inputting the role ids wrong?

[suresh4iam (Suresh Kumar Palanisamy)]

My understanding is that PATCH a specific role API will apply to an ID not to multiple IDs, that is the reason the API considering only the last ID and updating it from your bulk path param list. So, you need to set the path param dynamically to get the Role IDs and execute the PATCH operation for each role by using pre-request scripts. You can get the Postman documentation by searching “set-path-param-dymanically” and mostly it will be a few lines of code.

[jared-fox]

Thank you Suresh, that’s what the documentation makes it sound like too. You’ve been super helpful! I will look into the dynamic path parameters. A coworker advised me to try a powershell script to make the api calls and loop through the ID numbers from a CSV file. I will keep playing around until I figure it out.

[Sandeep2025 (Sandeep Patel)]

Hello Jared,
I would suggest using Bulk Role Importer tool If you want to add entitlements to 130 Roles.
Please let me know if you have any questions.

Thanks

Sandeep

[jared-fox]

Hey Sandeep,
I am looking over the documentation and it doesn’t seem very clear for someone at my skill level. I could probably figure it out if I spent a few days on it, but I think I will do them one at a time via API calls for now. I am always practicing my coding, but I’m not too familiar with Ruby and kind of a beginner. I look forward to trying this out in the future though.

Thanks for your input and making me aware of the bulk role editor!