function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Amit Khanduri.Amit Khanduri. 

Do i need to change https://www.salesforce.com/services/Soap/u/30.0 to http://login.salesforce.com/services/Soap/u/30.0 ?? as

As per www.salesforce.com API Endpoint Retirement https://help.salesforce.com/HTViewSolution?id=000229717 ?? we need to use login.salesforce.com. but when i changed https://www.salesforce.com/services/Soap/u/30.0 to http://login.salesforce.com/services/Soap/u/30.0 API is not working for Us. any help ???
pconpcon
Are you having problems with the login or with subsequent calls.  You will need to use https for your call.  If you are having problems with your calls after login you should be using the instance URL and making calls to that.  For example you'll get an instance URL of na7.salesforce.com you will make calls to https://na7.salesforce.com/services/Soap/u/35.0
Amit Khanduri.Amit Khanduri.
@pcon Thanks, This https://www.salesforce.com/services/Soap/u/30.0 Url is working fine for us but when i changed it to http://login.salesforce.com/services/Soap/u/30.0 as per salesforce api retirement guidlines Api is not working. 
could you please explain me how to change ?? yes we are facing in login.
pconpcon
Are you using http (as your link above states) or are you using https?
Amit Khanduri.Amit Khanduri.
We were using http just now i informed our application team to change it to https in integration part, and wating for the results. 
I appreciate your prompt response. Thank you will let you know.
Andy BoettcherAndy Boettcher
Amit,

You WILL need to change the "www" to "login" before January this year.  Salesforce is removing the "www" from responding to API calls.
Amit Khanduri.Amit Khanduri.
Sure @Andy Boettcher .. Thank you :)
Bhushan LaddadBhushan Laddad
Hi,
We had similar issue where we could connect succesfully to http://login.salesforce.com/services/Soap/c/13.0 but we were getting error when we tried to connect to https://login.salesforce.com/services/Soap/c/13.0 (500-time out error). So we have opened case with SF, so they said we should check our n/w settings and also they said SF would support ONLY https://login.salesforce.com and not http://login.salesforce.com after 01/01/2016.
Case  ID: 12859832
Amit Khanduri.Amit Khanduri.
We  have changed it do https://login.salesforce.com and its working fine.. Thanks All