Salesforce provides 2 WSDL (Web Service Description Language) files. They are called 'Enterprise WSDL' and 'Partner WSDL'. A WSDL is an XML document that contains a standardized description of how to communicate using a web service (the Salesforce API is exposed as a web service). The WSDL is used by developers to aid in the creation of Salesforce integration pieces. A typical process involves using the Development Environment (eg, Eclipse for Java, or Visual Studio for .Net) to consume the WSDL and generate classes which are then referenced in the integration.
1. The Enterprise WSDL is strongly typed.
2. The Enterprise WSDL is tied (bound) to a specific configuration of Salesforce (ie. a specific organization's Salesforce configuration).
3. The Enterprise WSDL changes if modifications (e.g custom fields or custom objects) are made to an organization's Salesforce configuration.
For the reasons outlined above, the Enterprise WSDL is intended primarily for Customers.
1. The Partner WSDL is loosely typed.
2. The Partner WSDL can be used to reflect against/interrogate any configuration of Salesforce (ie. any organization's Salesforce configuration).
3. The Partner WSDL is static, and hence does not change if modifications are made to an organization's Salesforce configuration.
For the reasons outlined above, the Partner WSDL is intended primarily for Partners.
Downloading a WSDL file when logged into Salesforce
Classic:
1. Click Setup | Develop | API
2. Click the link to download the appropriate WSDL.
3. Save the file locally, giving the file a ".wsdl" extension.
Lightning:
1. Click Setup | Integrations | API
2. Click the link to download the appropriate WSDL.
3. Save the file locally, giving the file a ".wsdl" extension.
000385303

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.