Definition
A WSDL (Web Services Description Language) file in Salesforce that is strongly typed and includes all standard and custom objects, fields, and types specific to your org, used for SOAP API integrations.
Real-World Example
a senior developer at TerraForm Tech uses Enterprise WSDL to solve a complex business requirement that cannot be addressed with declarative tools alone. They implement Enterprise WSDL with proper error handling, write 98% test coverage, and document the solution for future maintainers. The code passes security review on the first attempt.
Why Enterprise WSDL Matters
An Enterprise WSDL (Web Services Description Language) is a strongly typed XML file generated for a specific Salesforce org that describes all the standard and custom objects, fields, and types in that org. It's used for SOAP API integrations where external applications need to interact with Salesforce data. Because it's strongly typed, the WSDL gives client applications full type information for the org's specific schema, enabling type-safe code generation and compile-time checking.
The Enterprise WSDL is contrasted with the Partner WSDL, which is loosely typed and works against any Salesforce org without containing org-specific schema. Enterprise WSDL is the right choice when an integration is built for a specific org and benefits from the type safety; Partner WSDL is the right choice when an integration needs to work across multiple orgs without regenerating WSDL files. SOAP API itself is largely legacy now, with most modern integrations using REST API or other approaches, but Enterprise WSDL remains relevant for legacy SOAP integrations.
How Organizations Use Enterprise WSDL
- •TerraForm Tech — Uses an Enterprise WSDL for a legacy SOAP integration with their data warehouse. The strongly typed schema gave them compile-time checking against their custom objects.
- •CodeBridge — Migrated from Enterprise WSDL SOAP integrations to REST API for newer projects, treating SOAP as legacy.
- •Quantum Labs — Regenerates the Enterprise WSDL whenever they change custom objects significantly so the dependent integration stays in sync with the schema.