# How do I disable the SailPoint source?

**URL:** <https://developer.sailpoint.com/discuss/t/how-do-i-disable-the-sailpoint-source/1198>\
**Category:** SHF Discussion and Questions\
**Created:** [August 11, 2021, 7:49pm UTC](https://developer.sailpoint.com/discuss/t/how-do-i-disable-the-sailpoint-source/1198 "2021-08-11T19:49:18Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:47pm UTC](https://developer.sailpoint.com/discuss/t/how-do-i-disable-the-sailpoint-source/1198/4 "2021-09-09T19:47:13Z")

</div>

Hi @omar_khote_iam ,  
I’ve finally gotten back to this, since client wants it!  
I’m able to find the accounts by doing a search using  
a POST to /search?count=true&offset=1&limit=2 with the query:

> @accounts(disabled:false AND locked:false) AND (NOT attributes.cloudLifecycleState:"active"

and I pass the ID for the IdentityNow Source:

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

xxxx in this example to a POST /account/provision/xxxx

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 when after a refresh, the SailPoint source goes back to Enabled.

I’m going to open a separate ticket for the API call, since @omar_khote_iam was able to get past my initial question.

Thanks,  
Chris

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/how-do-i-disable-the-sailpoint-source/1198)._