Deprecation: CC, V1, and V2 API Decommission Update

Welcome to the Developer Community Pratyush. At this time, there are no replacements planned for that endpoint. You can find more information here.

Do we have an alternate API planned for the below?
/cc/api/user/loadAccounts

Hi, Can someone please suggest me if we have alternate API for these two:

{{baseUrl}}/cc/api/identityAttribute/update?name={attributename}
{{baseUrl}}/cc/api/source/loadAccounts/{SourceId}?disableOptimization=true

@colin_mckibben @colin_mckibben @tyler_mairose

oh I see this info from deprecated api list page.

{{baseUrl}}/cc/api/identityAttribute/update?name={attributename} - -- replaced by -->  /beta/identity-attributes/:name
{{baseUrl}}/cc/api/source/loadAccounts/{SourceId}?disableOptimization=true -->  extended till June 2024

Please correct me if there is any changes

You can track the replacement for this endpoint here.

That information is correct. Here are the relevant topics.

@colin_mckibben What is the replacement for

/cc/api/taskResult/get/ ?

The process I am using is triggering an entitlement aggregation on a source using /api/source/loadEntitlements (Which appears this API will be extended) and then checking the status of that aggregation using /cc/api/taskResult/get/

Is there a replacement for /cc/api/taskResult/get/

Or a recommendation for how to execute this process in a preferred way?

Thanks

Welcome to the Developer Community Jack! The replacement is listed here.

1 Like

Hi Team,

We have been advised that /api/v2/search/identities is still being used in our organization. We only have a few applications that are onboarded but not sure where is this end point being used? Will anyone be able to point us at the right place?

Thanks,
Abhi

Hi,

We are using /cc/api/source/loadAccounts to aggregate accounts on a source after another source account aggregation has been completed via a workflow. I did not seem to find a similar API in Beta / V3. Is there any similar API that can be used for this?

Hi,

The beta version of this api ( /cc/api/source/loadAccounts) is available now. Please check the link below.
import-accounts | SailPoint Developer Community

1 Like

Does this use / suport the same form-data paramaters as the former /cc/ version ? i.e. ā€œdisableOptimizationā€ and ā€œfileā€ ?

Is the ā€œfile upload utilityā€ for delimited sources updated to use the new API ?

(I don’t see documentation for the API in the postman collection)

Hi Scott,

I haven’t tested the File upload functionality as this is not a use-case which we have. But i did try the disable optimization and this working as expected.

Thanks
Jishnu

Great thanks Jishnu :slight_smile: The developer community notes show the BODY form-data options which look to match the /cc/ version usage so I’ll try it out.

1 Like

Hi Scott,

I found this link regarding File upload in another post. Please check if this helps your use-case.

1 Like

Hi, any update for /user/invite ???

9 Likes