Originally published May 16, 2019 Key Dates and Information End of Life Date: June 2020D2L Web Services was the first generation of API available to D2L clients. These APIs have been deprecated since the 10.3 release in 2013. Continued investment in Valence has reduced the need for the prior generation of APIs and we are making the decision to invest in a single API product moving forward. Why are we making this end of life decision?D2L Web Services has seen declining usage as Valence has increased in popularity and features. A very small number of clients remain using the tool in a very limited capacity. We believe that the small number of clients that remain using D2L Web Services would be better served by switching to Valence to take advantage of increasing features as well at ongoing bug fixes. What is the impact and transition plan for active clients?Clients actively using D2L Web Services will be required to switch those usages to Valence or decommission their D2L Web Services referenced code prior to the end of life date. D2L will be contacting those affected to ensure they have the information necessary to switch. We understand that time and developer resources will be needed for the change which is why is the end of life timeline is longer for this product. Frequently asked questions 1) Can I prepare for this change ahead of June 2020? Absolutely! If you are currently using D2L Web Services you should begin evaluating your usages and make the switch to Valence well in advance of June 2020. 2) What about any calls that Valence doesn’t have? We have identified that most of the functionality that previously existed in D2L Web Services now exists in Valence. A mapping of D2L Web Services calls to Valence calls can be found here: D2L Web Services mapping to Valence APIs 3) What if I’m an active user of D2L Web Services and need assistance evaluating what to use in Valence? Valence has a large base of D2L resources and client users who can answer questions as you get started. We recommend using the Valence documentation at: https://docs.valence.desire2learn.com/index.html as well as joining the developer community of practice at: [BROKEN LINK]https://community.brightspace.com/s/group/0F9610000001mZ1CAI/developers. Additionally, affected clients will be contacted directly to ensure they have the needed information and support for this transition.4) When will D2L Web Services stop working?June 1, 2020 D2L Web Services will be turned off for all clients and calls to the web service endpoints will no longer function.5) LTIAuthenticationTokenService is on the list, what is changing with it? The LTIAuthenticationTokenService SOAP route will no longer be accessible. There is a permission associated to calling the route which will be removed (GetTokenForCurrentUser). There is also three extended LTI parameters that were created for this route. The ext_d2l_link_id will remain in place while ext_d2l_token_id and ext_d2l_token_digest will be removed. 6) Why isn’t ext_d2l_link_id being removed? The extended LTI parameter, ext_d2l_link_id, is known to be used in some cases by vendors as a unique identifier for an LTI link. Due to this use case and the fact that it does not require any of the features of the SOAP web services to function, it was decided that it would remain in place. 7) Is Guid SSO included in the End of Life? Guid SSO uses the routes /d2l/guids/d2l.guid.2.asmx and /d2l/lp/auth/login/ssologin.d2l and is documented here: https://community.brightspace.com/s/article/Brightspace-Platform-Single-Sign-On-SSO. The Guid SSO is a separate tool not included in this end of life. 8) Are any other SOAP calls included such as those used by Holding Tank, IPSIS, or OrgUnitXML? No, the only routes affected specifically reference d2lws. The full list of routes to be removed can be found in the mapping document found here: https://community.brightspace.com/s/article/D2L-Web-Services-mapping-to-Valence-APIs. How Can You Provide Feedback Related to This Change?Leave a comment on this blog article!