Salesforce Developer Apis Soap


// Salesforce - Developer - APIs - SOAP:

Salesforce provides two SOAP API WSDLs for two different use cases. The 
enterprise WSDL is optimized for a single Salesforce org. It’s strongly typed, 
and it reflects your org’s specific configuration, meaning that two enterprise 
WSDL files generated from two different orgs contain different information.

The partner WSDL is optimized for use with many Salesforce orgs. It’s loosely 
typed, and it doesn’t change based on an org’s specific configuration.  
Typically, if you’re writing an integration for a single Salesforce org, use 
the enterprise WSDL. For several orgs, use the partner WSDL.

The first step is to generate a WSDL file for your org. In your DE org, from 
Setup, enter API in the Quick Find box, then select API. On the API WSDL page, 
click Generate Enterprise WSDL.

On the Generate Enterprise WSDL page, click Generate. When the WSDL is 
generated, right-click on the page and save the WSDL file somewhere on your 

The enterprise WSDL reflects your org’s specific configuration, so whenever you 
make a metadata change to your org, regenerate the WSDL file. This way, the WSDL 
file doesn’t fall out of sync with your org’s configuration.

// Creating a SOAP Project with SoapUI:

Now that we have our WSDL file, we need a way to extract the information to 
start making SOAP API requests. In web parlance, this process is called 
consuming the WSDL.  Tools such as Web Services Connector (WSC) 
consume the WSDL file. The tools then create classes that enable you to make 
requests with SOAP API using common programming languages.

We’re using a third-party tool called SoapUI to consume our enterprise WSDL file. 
SoapUI is a free and open-source app for testing web services. To get started, 
download and install SoapUI OpenSource from the SoapUI website. Install only 
the SoapUI component.

After you get SoapUI installed and launched, from the File menu, select New SOAP 
Project. For the project name, enter Exploring Salesforce SOAP API. For the 
initial WSDL, browse to where you saved the enterprise WSDL file and select it. 
Don’t change any other options.

Click OK. After a few seconds of processing, an Exploring Salesforce SOAP API 
folder appears in the navigator pane on the left side of the screen. Underneath 
it is an entry called SoapBinding that contains several operations.

Each operation corresponds to a SOAP API request we can make. The properties of 
each operation are pulled from information in the WSDL file. Each operation also 
contains a sample XML request that includes the operation’s HTTPS endpoint and a 
prepopulated SOAP message. Now we’re all set to make SOAP API requests.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License