Please let us know if there is any update on replacement of this API. This is critical for our project and we would like to get a replacement API sooner.
Itâs still in progress. I will report back once it is available.
I cannot run a non-optimized aggregation which is critical to the success of our go live of a new implementation in a few weeks. Is this functionality truly gone at the moment? It sounds like itâs being supported until June 14th but it doesnât seem to work for me in our tenant.
Welcome to the developer community Tim. This API will be supported until June 14th. If itâs not working for you, it might be a configuration issue on your end. You can ask for help in ISC Discussion and Questions to troubleshoot your issue.
@tjackson i just ran an unoptimized aggregation in our tenant so that end point is still active.
Hi Colin,
Do you have a date for the release of the replacement yet? Our development and test cycle is usually 6 weeks. Meaning if the replacement is not available by the end of April, then it is going to be hard to implement in our apps that use this API. Knowing the proposed date, will allow me to key up the required resources from my teams.
No firm date, but possibly as early as April 5th. If not this week, then next week.
I have a meeting with our Engineers on this API today, and I can provide an update if you like. I know this is still in testing on our side.
From discussions with SailPoint Engineering, they are wrapping up their testing. These new account aggregation APIs are being made available to me next week (April 8th) for testing the next version of File Upload Utility. If all goes well, they should be pushing to Production the following week (April 15th).
These are still tentative timelines and could change slightly depending on testing, but we know we are very close!
Thanks that is great to know, can you please confirm here once they are available in our tenants for customer testing thanks.
With changes made to the UI, we notice that the changes are first available to the sandbox environments before it is made available to the production environments. This allows us to see and communicate any issues with the new functionality, after which SailPoint can delay the release in production and ensure our production environment is not broken.
If I read your statement correctly, for this API, it will not first be available in our sandbox environments first, but directly in our production environments? If so, how else can we detect issues with the API prior to the release to production?
Kind regards,
Angelo
It is available to sandbox tenants right now actually. It should be available next week to production, along with documentation, etc. Once this is available you have until June (if I recall correctly) to carry out changes with the new APIs - in both sandbox and production.
Is there already some documentation on the new endpoint? I donât see it available yet in de API docs?
Alternatively, can you provide the new end point?
Hello @neil_mcglennon Can you please provide the new endpoint?
I have not found anything related to that endpoint in the documentation, and the browser developer mode still shows that the /cc/api/source/loadAccounts endpoint is being used for aggregations.
The replacement is still going through code review and testing. We will update this post once a replacement is ready.
Hi all! From what I have been told, the new API for account aggregations has been released for Sandbox and Production tenants. The new API is: POST /beta/sources/{id}/load-accounts
, and it sounds like new API documentation should also be released to that effect today. Iâve been personally testing this end-point with the new version of File Upload Utility (4.0) and all looks promising so far.
The only thing holding the new version of File Upload Utility from release is the entitlement aggregation endpoint, which we expect to be POST /beta/sources/{id}/load-entitlements
. We already have that new end-point coded into the File Upload Utility (4.0), and are awaiting some work on the SailPoint side to continue testing. We expect that new API to be available next week potentially.
If everything goes well, we should have File Upload Utility 4.0 ready with new APIs ready for the field by end of next week.
The new beta API doesnât seem to be tracking the identity that started the aggregation properly.
The User is âSystemâ in the sourceâs aggregation activity log and the Actor is blank in search for the corresponding âAggregate Source Account Startedâ event. Calling the deprecated API places the UID or alias of the identity that started the aggregation in both of these locations.
The new beta API documentation is available here:
Thanks @nsorlien - I alerted our Engineering teams about this nuance, and Iâm hoping it is something they should be able to address in short order. Stay tuned.