When selecting “Remove Account” on a user’s Accounts tab, this makes a POST call to:
https://org.api.identitynow.com/cc/api/account/remove/{{account-id}}
Is this the same functionally as /beta and /v3/accounts{{id}} DELETE?
The delete account API only works for flat file sources. The endpoint you shared is different. It will remove any account from the identity, regardless of source type. This is a gap that we need to close in our v3 API. If you don’t mind, can you please Ideas for this so our product team is made aware of the gap?
I would exercise caution if you decide to use the /cc API. Those APIs are unsupported and can change or disappear with little to no notice.
1 Like
@colin_mckibben , hi,
We also have to use that cc endpoint actively. Could you advise please about the draft estimated dates when it would be avaliable as at least beta API equivalent endpoint (if it is not already in)?
With best wishes,
Dimitri
Delete accounts is still in the backlog of APIs that need to be deprecated. There will be a v3 equivalent at some point. You can monitor this category for new deprecations: API Deprecations - SailPoint Developer Community Forum
Hi @colin_mckibben ,
As far as I understand, /cc/api/account/remove/:id removes the object link between an Identity cube object and a source shadow copy of connector account object.
Dimitri
Hi Colin
We need to delete tens of thousands of identities each year. What is the recommended approach for that once you close the gap and remove the /cc API?
There will be a v3 replacement when we deprecate the cc API. As of now, the cc API hasn’t been deprecated.
1 Like