This API’s shutoff date has been extended to November 1st.
The replacement API is
For a full mapping of /api/app replacements, please see this doc
IDN-V2024 Public Preview Apps API mapping from legacy CC endpoints-090924-215538.pdf (595.0 KB)
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.
Hi,
I have just found this topic looking for solution to my problem. I use https://xxxxx.identitynow.com/cc/api/app/create endpoint to onboard an Application.
Sending a sample payload fails:
{
"name": "Just test Application",
"description": "Global, centrally supporting db-backed web application"
}
It used to work OK, but I am constantly getting an unknown (to me) error message:
{
"msg_template": "Cannot get property 'alias' on null object",
"slpt_error_code": "SLPT-1005",
"formatted_msg": "(SLPT-1005) Cannot get property 'alias' on null object",
"exception_id": "18CE9BCD3FD",
"error_code": 1005,
"exception_class": "java.lang.NullPointerException",
"exception_detail": {
"file": "AppService.groovy",
"method": "createApp",
"line_number": 466,
"class": "com.cloudmasons.AppService"
},
"http_response_code": 500,
"timestamp": "2024-01-08 15:41:55.581",
"exception_message": "Cannot get property 'alias' on null object"
}
Do you have any clue what really is missing? I cannot find any documentation on SailPoint site regarding this endpoint.
Any help highly appreciated. Thank you!
–
MF
Welcome to the community Mariusz.
This endpoint is deprecated and will be turned off on March 31st. I do not recommend you continue using this endpoint in your application. There is a v3 replacement being worked on that will be available soon. I suggest you wait for this new endpoint to be available before continuing.
Colin,
Thank you for your fast response. I will wait for update.
Is there any exposed v3 replacement that I could use and test?
This would help me a lot 
MF.
Hello Colin,
I am also using the cc application creation & update API,
what is the release date for the V3 version? is it planning to be published this month before the cc will be turned off so we can prepare?
Thanks,
Limor
Do we have any update on the availability of the api ??
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.
@colin_mckibben Not sure if this is the right forum for this, but for the current Application API, in general, it seems like app data is aggressively cached which has caused us some headaches in the past. For example, the simple example of creating an app “My App”, renaming it to “My App OLD”, then trying to create a new app named “My App” will fail saying “My App” already exists, even though the original app had been renamed. We’ve also seen issues where a deleted app is still showing up in the API with any additional attempts to delete it failing with “the app doesn’t exist”. Hopefully this is a known issue and being addressed in the new API, but if not…could you help get this info to the developers? Thanks!
Please share the endpoint for the replacement API? has it been released yet as planned?
Did you resolve this error? I am experiencing the same behavior. It does appear that the API is broken. @colin_mckibben we understand this endpoint will be deprecated and shutoff date is August, however, it seems to be broken. Any ideas for a workaround in the short term?
is there an update for this call?
@colin_mckibben is replacement for this API POST /ears/apps/source-apps? When I try using this endpoint with old credentials, I am getting 401. Is there anything different authentication-wise compared to the old API?
Please provide a status.
We also see issues with the V1 Application apis.
It feels like there are issues with the current soon to be deprecated API that are not being worked on because it will be replaced, but a replacement keeps sliding.
We have been in a ‘holding pattern’ for some time, and the Plane does need fuel…
Do I continue to enhance / gap fill ISC via the v1 api?
Hi Muharem,
That is not the public replacement endpoint. Once a public replacement is made available (estimated to be available later this month as per the post above), there will be supporting API specs published and a link will be provided in the top post. Any new public replacement endpoints will follow the authentication guidelines here.
Hi Christine,
thank you for the update.
Hello everyone,
I hope I’m in the right place for this post—apologies if not.
We are encountering an issue with the /api/app/create endpoint. Despite providing the required name and description attributes in the payload, the endpoint consistently returns a 500 Internal Server Error.
Has anyone else experienced this issue or found a solution?
Thank you for your assistance.
Any update on when the replacement API call for this will be available? I’m seeing “end of June” with the API being replaced extended to Sept…however the original is not working for one of my customers…
Following 3 API endpoints are the once we have issues. Simply put we are looking for direction in which version of the API should be used and KBs describing how the API should be used instead the bellow. Once we make sure we are using the correct endpoints we will post screenshots/errors of our experience.
/cc/api/app/create - not working
/cc/api/app/update/{sourceId} - not working
/cc/api/app/delete/{id} - not working (does not return any error, but does not have any effect)
These are API endpoints we are using today, most working, some not.
/beta/task-status
/beta/access-profiles
/beta/entitlements
/cc/api/app/create - not working
/cc/api/app/update/{sourceId} - not working
/beta/access-request-status
/beta/access-profiles/{accessProfileId}
/beta/entitlements/aggregate/sources/{id}
/beta/access-profiles/{id}
/cc/api/app/delete/{id} - not working (does not return any error, but does not have any effect)
/v3/accounts
/beta/workgroups
/beta/identities
/beta/sources/{id}/load-accounts
/oauth/token
As you can see from the list, /cc/api/app is not working for our organization. We would like to ask for a Zoom/Meet working session to troubleshoot
We are also using BETA endpoints which i’m sure is not the correct ones. Can you or you team tell us which V3 endpoint maps to the BETA ones?
Thank you
Hi @bernardo-camargo, if you are encountering issues with this API, please open a support ticket so that we can triage and gather more details to help find a resolution.