v2024 experimental endpoints will be available by end of this week. Both beta and v2024 experimental may change with little to no notice. Please see our API versioning strategy for more information.
The replacement for this API will be available by the end of June, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to August 30th.
The replacement is not yet available. I will update this post once one is available. We are extending the shutoff date of the CC API appropriately to allow users enough time to migrate to the new endpoint.
The top post still mentions that it will be available at the end of this month, which is tomorrow.
If this is definitely not going to be the case anymore, could you please update this post with the new availability date?
And if SailPoint does not have a new availability date or an estimation (Days/Weeks/Months?) when it might become available, please let us know this as well such that we can plan our strategy accordingly.
I have asked engineering for an updated ETA, and they will come back with an answer by the end of day. There have been some unforeseen issues during the creation of the replacements that have delayed the rollout. I will update the topics once I have a new ETA.
The replacement for this API will be available by September 3rd. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to November 1st.
Hi @colin_mckibben ,
I am using this API in my script as below. sometimes its work but sometimes I am not getting exact response from this API.It seems to be working intermittently.
foreach ($app in $appResponse) {
$appID = $app.id
$appName = $app.name
Write-Host "Application Name :" $appName `n"Application Id :" $appID
$IDNApps = Invoke-RestMethod -uri "https://OrgName.api.identitynow.com/cc/api/app/get/$($appID)?_dc=$($utime)" -Method GET -Headers @{Authorization = "Bearer $($idnPRODSecret)" } -ErrorAction Stop
#$IDNApps | ConvertTo-Json
$ownerName = $IDNApps.owner.name
Write-Host "Application Owner name :" $ownerName
#####access profile in each application####
$appAccessProfileURI = "https://OrgName.api.identitynow.com/cc/api/app/getAccessProfiles/$($appID)?_dc=$($utime)"
$appAccessProfileResponse = Invoke-RestMethod -uri $appAccessProfileURI -Method Get -Headers $PRODheaders
if ($appAccessProfileResponse.count -gt 0) {
foreach ($accessProfile in $appAccessProfileResponse) {
$appAPname = $accessProfile.items.name
$appAccessProfilenamelist = $name -join ";"
Write-Host 'Access Profile Name:' $appAPname
Write-Host "Access Profile list :`n" $($appAccessProfilenamelist)
}
}
I have discovered that the following APIs are giving data, despite that the documentation is missing
GET /beta/source-apps GET /beta/source-apps/:id GET /beta/source-apps/all
I haven’t checked if the POST, PUT, PATCH, DELETE operations are responding yet, but calling the OPTIONS on it yield the following, so it looks promising:
Tha API new strategy consists on releasing a new API collection every 3 years (v2024, v2025, etc.) and for example beta and v3 will be useless from 2027.
But, what to do about the workflows already existing with HttpRequests using Beta/v3 API calls ? Will we be obliged to modify them manually ?
Hi @angelo_mekenkamp ,
Do we have any API which provides application name from an Access Profile?
For example:
We have a source which consists of multiple applications.
Like Source AD and having respective App name: APP1, APP2, APP3. and below access profiles mapped with these applications.