Deprecation: Non-Public API Deprecations (CC, V2)

Hi @GiuseppeDe
Can you confirm which API you are referencing as the " v3/beta api" above? I want to be sure we are looking at the same endpoint. Then I will have the team review. Thank you!

Hi @angelo_mekenkamp ,

Thank you for taking the time to share your feedback. The suggestions you have made are valid, and are something that we will strive to provide, but given the tight deadline to deprecate the non-public endpoints, most of our focus and effort is on publishing appropriate v3 endpoints to replace them. The sooner we get them published, the more time our users will have to migrate.

To keep the communications focused, we initially decided not to post the full list of non-public APIs we intend to deprecate without a replacement ready to go. However, I can work on getting a full list of non-public APIs to better prepare users.

Deprecation headers are something we plan to make standard for our V3 APIs for the exact reason you mentioned. However, it is not something we have planned for our non-public APIs. This would detract from the effort to provide the v3 APIs. Please subscribe to the API deprecations category to get notified when new endpoints are deprecated.

2 Likes

Hi Joshua,

If I use /cc/api/integration/listSimIntegrations I get back a list with one element which is my sdim.
If I use /v3/service-desk-integrations or /beta/service-desk-integrations I get back an empty list.
Just for info my sdim is used to connect to HP Service Manager with a custom connector.

Regards,
Giuseppe

@colin_mckibben ,
May I ask to confirm if CC API [tenant].api.identitynow.com/cc/api/event/list also under a development to be represented in v3? ‘Seach’ current API fof events scope is not the same as a ‘Search’ interface database has a timelapse gap sometimes up to 24h sometimes in syncing with real action status of IDN.

With kind regards
Dimitri

@kenilelk1 /cc/api/event/list has not been evaluated for deprecation yet, but the current limitations in search will be considered when designing a replacement.

1 Like

I’d like to also add another vote for a production equivalent endpoint for. We have over 30 sources for certification and for role based access control. We would be happy to use direct connected sources but unfortunately 80% of our sources do NOT have any direct connected sources. And we have to follow SailPoint professional suggestions to use these APIs heavily in our auto transformation process,

Please, please help create an v3 replacements,

/cc/api/source/loadAccounts
/cc/api/source/reset/$source_id
/cc/api/source/loadUncorrelatedAccounts/
/diana/sources/uncorrelatedAccounts/
/cc/api/campaignFilter/create

@colin_mckibben , Hi Colin, is there any update on disableOptimization api. What api should be used?

@yannick_beot, FYI, I noticed that the VSCode IDN plugin uses
https://tenant.api.identitynow.com/cc/api/source/reset to reset sources, entitlements and accounts:

You may want to watch this article and plan ahead (if you’re not doing it already), to avoid broken functionality in your plugin.

Hi, does anyone know if non-public API’s (/cc/api) are officially supported?

we have one source where /cc/api/source/exportAccountFeed/{:id} is only returning the header row, and no records. No idea why, or how to fix this.

Thanks

You can try submitting a support request, but since they are being deprecated you might want to try and move off of it. Are you just trying to get accounts for a source? You can use list-accounts | SailPoint Developer Community and use pagination to get all of the accounts for a source.

Thanks Colin, I will do that and then convert/reformat to CSV

1 Like

Check out this video to learn how you can use the SailPoint SDK to extract accounts into a CSV file. It might save your some time.

1 Like

5 posts were merged into an existing topic: Important: CC, V1, and V2 API Decommission Update

If you have any questions about this announcement/topic, please see our newest announcement for updates and discussion: