I too get this same error. The details page is using the /cc/api/user/enabled API to disable an identity, which results in the error with a bunch of items that the identity doesn’t own. If I disable the same identity from the identity list, then it works. The identity list uses the /beta/identities-accounts/{id}/disable API. I think this is a bug and should be reported to the support team. Can you please open a support ticket?
Hi @colin_mckibben@atarodia
We are also facing the same issue while we are disabling the identity using cc API from a script. Please let us know once the issue got fixed or else suggest us so that we can also create a case for the same.
Thanks
Narendra
If you are using the cc API in a script, then I recommend switching to the beta API. That will fix your issue immediately while also getting you off of the private API.
Hi @colin_mckibben
Thanks for the response and we looking to replace the cc API with beta API. Does this cc API for enable is going to be deprecated and can we consider the beta API as an alternative.
Please let me know your inputs.
Thanks
Narendra
It is not yet deprecated, but I suspect this /cc endpoint will be deprecated in the near future. I think you will be better off migrating to the beta endpoint in preparation for a v3 replacement.