+ Start a Discussion
Nikolai LombaardNikolai Lombaard 

php webtolead form soap client api integration

Hi All,

We've implemented a custom solution for our web to lead form using the soap client rather than an API form post solution.

We've received a request that the API references need to be updated and need to understand what should be updated  within the soap client wsdl's setup.

Could we manually make these changes or could we download and updated soap client with these references already in place.
Best Answer chosen by Nikolai Lombaard
srlawr uksrlawr uk
If you are hitting the SOAP API directly for Lead insertion, you should probably be alright from the webto.salesforce.com point of view (which is redirecting the standard W2L POSTs)... however, you will want to make sure the WSDL login URL is now "login.salesforce.com" instead of "www.salesforce.com" - you can try to dig this out in your WSDL and update it, or just consume a new one (which might have other ramifications!)

You could also possibly sniff/debug the calling out system or network traffic to see what endpoint it is connecting to?

All Answers

srlawr uksrlawr uk
If you are hitting the SOAP API directly for Lead insertion, you should probably be alright from the webto.salesforce.com point of view (which is redirecting the standard W2L POSTs)... however, you will want to make sure the WSDL login URL is now "login.salesforce.com" instead of "www.salesforce.com" - you can try to dig this out in your WSDL and update it, or just consume a new one (which might have other ramifications!)

You could also possibly sniff/debug the calling out system or network traffic to see what endpoint it is connecting to?
This was selected as the best answer
Nikolai LombaardNikolai Lombaard
Meaning if the current sForce SOAP API remains as "https://login.salesforce.com/services/Soap/......" the endpoit should remain intact.
srlawr uksrlawr uk
Yep, that looks good to my understanding of things!