In Summer ‘27, the SOAP API login() call in SOAP API versions 31.0 through 64.0 will no longer be supported and no longer be available.
Where: This change affects these SOAP API versions:
31.0, 32.0, 33.0, 34.0, 35.0, 36.0, 37.0, 38.0, 39.0, 40.0, 41.0, 42.0, 43.0, 44.0, 45.0, 46.0, 47.0, 48.0, 49.0, 50.0, 51.0, 52.0, 53.0, 54.0, 55.0, 56.0, 57.0, 58.0, 59.0, 60.0, 61.0, 62.0, 63.0, 64.0
This change applies to Salesforce Classic and Lightning Experience in all API-enabled Professional, Enterprise, Performance, Unlimited, and Developer editions.
When: You can continue to use login() in SOAP API versions 31.0 through 64.0 until Summer ’27 is released. At that time, login() in these SOAP API versions will be retired and unavailable. When login() in these SOAP API versions is retired, applications using login() in these SOAP API versions will experience disruption. The requests will fail with an error message indicating that the login() endpoint has been deactivated.
How: Before Summer ’27 is released, customers and partners must modify or upgrade their applications to use external client apps for authentication. See SOAP API login() Retirement.
Test the retirement’s impact on your org by enabling the test run in release updates. The test run disables the SOAP API login() call in your org.