What changed?
Salesforce retired the SOAP API legacy versions:1.8, 2, 2.2, 2.5, 3, 4, 5, and 6 no longer be supported with the Winter ‘19 release. Customers could use these legacy versions until Winter ‘19 when these legacy versions become unavailable. Applications using legacy versions of the SOAP API will experience disruption. The API calls made to these legacy versions will fail and result in an API error indicating that a particular version has been deprecated.
What action did I need to take?
Before the Winter ‘19 release, customers needed to upgrade their applications to include the latest SOAP API version available to prevent disruption to applications currently using the legacy versions. Moving to newer versions of our SOAP API will offer advanced capabilities with improved security and performance.
For information on accessing the latest SOAP API versions, see the Introducing SOAP API Developer Guide.
How did I know if versions of the Legacy SOAP API were used in my applications?
To identify applications using Legacy SOAP API versions, contact the developers of applications you use in your org to determine what SOAP API versions are being used.
If you can't contact the developers of your applications, you can review your event logs from your Salesforce orgs by following these steps:
Use a tool such as Workbench to run a query against the EventLogFile object, which will provide you with a log of all actions taken within your org during the last 24 hours.
Export and download the data into a .CSV file.
Open the CSV file and look for the log lines with an API event with API_TYPE equal to either E or P.
In that record type, there will be a column that displays the version of the API used. This API retirement will impact any integrations using version 6 and below.
For more information, see the How to Download and Visualize Event Log Files Trailhead Module.
Why did we retire this product?
We focused our development efforts on enhancing our latest SOAP API versions to improve the overall Salesforce experience to build custom functionality via applications.
How can I get more information?
If you have more questions, open a case with Support via Salesforce Help. To view all current and past feature retirements, see Salesforce Feature Retirement.
To read about the Salesforce approach to retiring products and features, read our Feature Retirement Philosophy.
000382872

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.