# Disable SailPoint Source Status API call

**URL:** <https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527>\
**Category:** SHF Discussion and Questions\
**Created:** [September 9, 2021, 7:52pm UTC](https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527 "2021-09-09T19:52:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisp](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@chrisp](https://developer.sailpoint.com/discuss/u/chrisp)\
**Post date:** [September 9, 2021, 7:52pm UTC](https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527/1 "2021-09-09T19:52:46Z")

</div>

I am calling the API: /account/provision/:id with the id from a search result, xxxx in this example:

> “id”: “xxxx”,  
> “source”: {  
> “name”: “IdentityNow”,  
> “id”: “yyyyy”,  
> “type”: “IdentityNowConnector”  
> },

This APPEARS to work, since the SailPoint source is showing as Disabled in the UI.  
BUT, it doesn’t really update the source. I get the same number of identities when I run the query, and after a refresh, the SailPoint source goes back to Enabled for he user.

Is there something else that needs to be done?

Thanks,  
Chris

---

<div class="post-metadata">

**Author:** ![chrisp](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@chrisp](https://developer.sailpoint.com/discuss/u/chrisp)\
**Post date:** [September 9, 2021, 8:03pm UTC](https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527/2 "2021-09-09T20:03:06Z")

</div>

Some additional information.  
Here is the body from the POST call:

> {  
> “accessRequestId”: “aaaaaaa”,  
> “caseName”: “Cloud LCM Provisioning”,  
> “launchStatus”: “executing”,  
> “launcher”: “Chris.Peterson”,  
> “messages”: ,  
> “resultDetails”: {  
> “attributes”: {  
> “identityRequestId”: “bbbbb”,  
> “workflowCaseId”: “ccccc”  
> },  
> “completed”: null,  
> “completionStatus”: null,  
> “created”: 1631213057104,  
> “description”: “Workflow Case”,  
> “id”: “ddddd”,  
> “launched”: 1631213056745,  
> “launcher”: “Chris.Peterson”,  
> “messages”: ,  
> “name”: “Cloud LCM Provisioning - 9bb1d2ce1876452a8d4bbf173a3e50c5”,  
> “parentName”: null,  
> “progress”: null,  
> “returns”: [  
> {  
> “attributeName”: “case”,  
> “displayLabel”: “CASE”  
> }  
> ],  
> “type”: “QUARTZ”  
> },  
> “sessionOwner”: null,  
> “variables”: null  
> }

And the user has a “Disable Account Passed” Action for the IdentityNow Application in the Activity tab. But the Account is still showing as Enabled.

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [September 10, 2021, 1:46pm UTC](https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527/3 "2021-09-10T13:46:14Z")

</div>

I’m not familiar with this API. Is it a v3 or beta?

---

<div class="post-metadata">

**Author:** ![chrisp](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@chrisp](https://developer.sailpoint.com/discuss/u/chrisp)\
**Post date:** [September 10, 2021, 2:41pm UTC](https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527/4 "2021-09-10T14:41:31Z")

</div>

The base is:

> [https://tenant.api.identitynow.com/cc/api](https://tenant.api.identitynow.com/cc/api)

and it’s a POST for /account/provision/:id  
with the postData: “disabled=true”

This is what the UI is using for the Disable Account on the Accounts tab.

Thanks,  
Chris

---

<div class="post-metadata">

**Author:** ![chrisp](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@chrisp](https://developer.sailpoint.com/discuss/u/chrisp)\
**Post date:** [September 12, 2021, 4:07pm UTC](https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527/5 "2021-09-12T16:07:04Z")

</div>

I think this may have been caused by another issue with our tenant, whicjh caused some actions to be inconsistent. That has been corrected, and now the API call works to successfully disable the account.

When I did the disable through the API, and through the UI, the accounts stayed disabled after a Refresh.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [July 19, 2023, 2:22pm UTC](https://developer.sailpoint.com/discuss/t/disable-sailpoint-source-status-api-call/1527/6 "2023-07-19T14:22:03Z")

</div>