Retirement of API endpoint


If you are an administrator of a Salesforce org, you might have received the reminder email below. The email states that as of January 1, 2016, the API endpoint will be retired. This reminder is not applicable for Connexys orgs. You and/or your organisation will not have to take action.


As an admin of a Salesforce org, we want to notify you of an important change to the availability and support of as an API endpoint. 

What is changing?
Currently, customers can use as an API endpoint that will route them to the correct instance. As of January 1, 2016, the internal routing will be retired, and any API endpoints will need to be changed if from to

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 do I need to take?
Update your integrations to replace with, as the official endpoint for the Salesforce API.

Please see the 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.

How can I get more information?
For additional questions, you can open a case with Customer Support via the Help & Training portal.

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

Any unreleased services or features referenced in this or other press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase Salesforce applications should make their purchase decisions based upon features that are currently available.

Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk