Reset Source accounts API

Feedback General Feedback
,
1

It’s a bit difficult to find the new API to reset source accounts.
Eventually, through the API deprecation list, I found delete-accounts-async | SailPoint Developer Community.
Which is titled ’ Remove All Accounts’ under the ‘Accounts’ tab, with a URL of ‘delete-accounts-async’, while actually being a ‘remove-accounts’ endpoint that in my opinion should be under the ‘Sources’ API list.

Can you please clean this up as it’s quite hard to find… :slight_smile:

1 Like
2

This is a good observation. I have just updated the specs to put the remove accounts API under the “Sources” collection. The changes should be live in about an hour.

3 Likes
3

Love the interactivity and effectiveness of this developer forum, thanks for the quick feedback and fix Colin!

2 Likes
4

Hello @colin_mckibben ,
I just tried the request, unfortunately I get 400.
I have counter-checked the source Id and the request seems good to me. Here the error am getting
detailCode": "400.1 Bad request content

“text”: "Action "Remove Source Accounts" cannot be performed on

Your help would be greatly appreciated.

5

It looks like your error message was cut off. Can you please provide the complete error message along with the details of the request? What type of source are you trying to reset?

6

Hi Colin,
The connector type is JDBC.
And the postman request is POST, with the following details:

https://{{baseurl}}beta/sources/e7ww51y8f87487e91f912998a4196a9/remove-accounts

Response

{
"detailCode": "400.1 Bad request content",
"trackingId": "b33f2ee39fca4db0a094b2613e31a81f",
"messages": [
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "Action \"Remove Source Accounts\" cannot be performed on [d8e7f7b84538465c935fca35101d7519]"
},
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "Action \"Remove Source Accounts\" cannot be performed on [d8e7f7b84538465c935fca35101d7519]"
}
],
"causes": []
}

Thanks

7

I’m not aware of any limitations with removing accounts from a JDBC source. You should open a support ticket so the support team can investigate the logs.