Hi All,
First, we thank you for your patience as we recognize that the Non-Public API Deprecations have required that many of our customers take action to accommodate changes to call our updated public APIs that that are used in their implementations. The public APIs replace outdated APIs with more secure and performant APIs that will allow us to support our customers more effectively in the future.
In regards to the deprecation of the /api/source/loadAccounts endpoint and its replacement:
- We heard your frustrations with a potential weeks’ long gap. The team has expedited the change to support x-www-form-urlencoded in POST /beta/sources/:id/load-accounts which would allow for disabling optimization via workflows. This has been enabled for all production tenants last night. If you still find issues, please flag this to me immediately so our team can react.
- We know that this endpoint’s deprecation in particular has had to get pushed out a couple times past our original deprecation date, and that was to accommodate a late replacement as a result of unforeseen engineering hurdles. We apologize for any inconvenience here.
- Customers should feel confident in leveraging Beta APIs in production. We release APIs in Beta to allow for our team to make updates to the APIs prior to versioning them, but our process requires that we provide advance notice if any breaking change is to be made prior to making a change so that our developer community is aware.
Again, thank you for working with this large API deprecation effort as our goal is to move forward together with better API support going forward. Please reach out to me and/or your CSM if you’d like to chat further.
Christine Whitlock
[email protected]
Sr. Manager, ISC Product Management