Our bi-weekly API Deprecation Office Hours are a great place to get help from the SailPoint Developer Relations team with migrating from CC, V1, or V2 APIs to our V3 APIs equivalents. If you have any questions about these APIs (e.g. object mappings, data types), how to change your API calls our for our SDKs, or anything else related to our API deprecations then this is the place for you to join and ask!
Hi, I was told by Sailpoint previously that all of the deprecated API’s will be given V3 or Beta equivalents before deprecation. Is this still true as cannot see a specific API to change Identity Status as per V2. There are also a few cc API’s not covered in V3 or Beta.
Great questions, and welcome to the developer community!
You are mostly correct in that all CC, V1, and V2 endpoints should receive a replacement before the APIs shut off on March 31st, 2024.
Those replacement APIs will come up in real-time as our engineering teams build the replacement endpoints. If you want to stay up-to-date in real-time on when those endpoints become available, subscribe to the #idn:api-deprecations category by going there, clicking the little bell in the top-right corner, and change your notification level to “Watching First Post”. This will allow you to get notified every time a new replacement endpoint becomes available.
We will also be holding these office hours four times a month for you to come and ask questions as well, so don’t hesitate to show up and let us know what endpoints you’re working with. We’re keeping a list of endpoints being discussed, and we’ll take that back to engineering to let them know what our community is doing.
Let me know if you have any follow-up questions—we’re here to help!
Do you guys happen to know if there will be a replacement for the following APIs:
Source resets. Here are the API calls for reference:
{{api-url}}/cc/api/source/reset/:cloudExternalId?skip=accounts
{{api-url}}/cc/api/source/reset/:cloudExternalId?skip=entitlements
refreshidentities and their arguments?
{{api-url}}/cc/api/system/refreshIdentities with the following payload:
It seems we are being pushed towards CLI, but it’s still using CC endpoints as well. Some of these endpoints are on my list of concerned methods that haven’t been ported over. I gotta assume CC will remain until methods CLI relies on are available, right?
Thanks Jason. I got to review the session where you discussed your usecase and the crux of it is similar to ours: downloading even ~30 campaign reports is an hours-long task, whereas a script that pulls them with that API call takes tens of seconds. This is essential for an automated email script that runs weekly when we run large quarterly campaigns, as well as to quickly provide bulk data to auditors.
Let’s say Campaign ID we want is 107e309a372943849a91a49acbfd432b
Generate latest reports for this campaign
POST beta/campaigns/107e309a372943849a91a49acbfd432b/run-report/CAMPAIGN_REMEDIATION_STATUS_REPORT POST beta/campaigns/107e309a372943849a91a49acbfd432b/run-report/CAMPAIGN_STATUS_REPORT
Get Report IDs
GET /v3/campaigns/107e309a372943849a91a49acbfd432b/reports
GET /v3/reports/c8705aa62c4d490f8c475756ff0f5bdf?fileFormat=csv
Response should be the CSV file
NOTE: The documentation page says to include header Accept:application/octet-stream - but I got error with this, so my headers are:
Authorization: Bearer …
Accept-Encoding: gzip, deflate, br