Print this page API Endpoint Retirement

Knowledge Article Number 000229717

What is the change?

Currently, customers can use as an API endpoint that will route them to the correct instance. As of February 14, 2016, the internal routing will be retired, and any API endpoints will need to be changed if you are using Note: This only applies to API traffic;  logging in from a browser by clicking “login” will still work.


Why are we retiring the internal routing?

This change is to ensure we focus our development efforts on delivering better performance and higher availability on the dedicated API endpoints.


What action must I take?

Update your integrations to use as the official endpoint for the Salesforce API. Please see Best Practices When Referencing Server Endpoints article.


What will happen if I do not take action?

The API will no longer function, and your API calls will result in a “404 (Page Not Found)” error.


Where can I find additional information?

For additional questions, you can open a case with Customer Support via the Help & Training portal.

Note: Web-to-Lead and Web-to-case is not affected by this change currently.

For an overview of our philosophy on retiring functionality, please click here.


promote demote