POST /api/app/update/{appId}

Identity Security Cloud (ISC) Non-Public API Deprecations
23

Response:

{'detailCode': '400.0 Bad request syntax', 'trackingId': '5ee8f4f19a2a45a69469596e992793ef', 'messages': [{'locale': 'en-US', 'localeOrigin': 'DEFAULT', 'text': 'The request could not be parsed.'}, {'locale': 'und', 'localeOrigin': 'REQUEST', 'text': 'The request could not be parsed.'}], 'causes': []}

Payload isn’t logged, but would’ve been something like:

{
            "accessProfileIds": ["accessprofile_id", "accessprofile_id1"...]
        }

Tried to run locally with similar data and got the same response

25

Can you share a screenshot of your request in Postman? I just want to make sure the payload is exact. Our engineers are unable to reproduce this issue unless they use double brackets:

{
    "accessProfileIds": [["669ab493853a441abecf0506365144b6", "7fa0549e27b941e68e63231f6d6f1193"]]
}
1 Like
26

Ok that’s bizarre, the last object in the list does have it’s own separate brackets:

{
            "accessProfileIds": ["accessprofile_id", "accessprofile_id1", ["accessprofile_id2"]]
        }

It’s a long python script that hasn’t been updated in a while so I’m not sure how it ended up breaking, perhaps some dependancy change.

Thanks for helping me troubleshoot!

27

Hello @colin_mckibben, could you please share the link to the new endpoint documentation ?

2 Likes
28

Hi Bastien,

I have found this endpoint documentation and others related to applications here:

2 Likes
29

Please don’t use the beta apps endpoints. These are the endpoints that will replace the cc apps endpoints, but they were mistakenly released as beta instead of v2024 preview. I am working with engineering to get them released in the proper version.

The endpoints themselves won’t change, so you can review them to see if they will work for your needs, but please don’t incorporate them into any production code yet.

1 Like
30

Why not?

All cc APIs have been or are being replaced by beta APIs and the beta APIs are being supported at least until 2027.

beta APIs are not meant for usage in production, but neither are the experimental v2024 APIs (although we know many customers still use the beta APIs in production simply because there is no production alternative provided).

Extrapolating from how long it took before production APIs became available to replace certain beta APIs (some crucial APIs like list identities don’t even have a production API yet) it could take many months or even years before production APIs are available.

My scripts have been built on the fact that you can distinguish production and nonproduction APIs by changing the URL. I also like that based on the URL you can directly see in the logs if you are using production or non production APIs. I understand we are forced to change the logic to cater for these design changes from SailPoint side, but at least we do have until 2027 for that.

1 Like
31

The replacement APIs are now available. Please see the first post for more details.

32

Hello, do we have to wait the v2024 version to implement it on our process ?

33

You can use the beta now, or wait until the v2024 experimental is available at end of this week. More information on our API versioning can be found here: API Versioning Strategy | SailPoint Developer Community

34

@colin_mckibben An endpoint to add an Access Profile to the Application seems to be missing.

35

Welcome to the Developer Community Daniel. I updated the first post to include an example of adding an access profile.

1 Like
37

Reminder, this API will be turned off on November 1st, 2024. Please make sure you migrate to the replacement API ASAP.