Hi Pooja,
Now looking at the screenshots from you last few posts, I am uncertain on things you did there, it was not how you meant to use the DX asset.
The following screen should be all you need to configure the asset to work. BPAPI_CLIENTID should be set to the exact name of the service account you created, which is also the same as the account with yellow key you can see from within Blue Prism user screen. You seem to be using many different values over time. I cannot be certain which is actually your API service account, and if sufficient permissions have been granted to it.
The asset should also have variables set so you do not need to enter any value, for example, on the next screen. But you chose to override the values here, and somehow you used "AuthenticationServer" on Client ID, which just does not make sense. This should be set to your API service account name instead, and if you have been using the asset in the way it is designed, you would have set that in the previous screen, against variable BPAPI_CLIENTID.
My assessment on your situation is that you did not plug in the authentication values and because of that you were getting 401. In this very case, 401 does not mean insufficient permissions, but rather incorrect credentials.
I would think you should check your service account, make sure you are using the right service account name for the asset. Once done, consider reimport the DX asset by overwriting the existing one, followed by reconfiguration of all parameters according the instructions given in the user guide and see if it works for you.
Lastly, you do not need to reset your IIS after making any changes anywhere. By design, obtaining a new oAuth 2.0 token is sufficient for the API services to take into consideration of updated permissions you have set in Blue Prism against your service account.
Hope this helps.
------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------