We have built a .NET app that uses our Enterprise WSDL to pull data from Salesforce , and we use a dedicated development sandbox for ongoing development.

Previously, looking at the WSDLs generated from the two orgs, in addition to the SOAP endpoints starting w/ login.salesforce.com vs. test.salesforce.com, the Id at the end, following the API version number, also used to be different between the two. I don't know what that Id refers to - it's not the Org Id, or I wouldn't be asking the question ... probably.

I just refreshed that dev sandbox and generated new WSDLs (Production/refreshed sandbox) and the endpoints are identical. Aside from the 'test' vs. 'login', does that last ID being the same matter anymore? (That dev team doesn't like to 'just try stuff out' w/o evidence -- engineers...)


  • Note: after generating them, the WSDL endpoints are exactly the same, just to be clear. Commented Mar 2, 2017 at 14:56
  • Possible duplicate of salesforce.stackexchange.com/questions/50148/… Commented Mar 2, 2017 at 15:02
  • WSDL describes state of an org. If you have 2 identical orgs -- wsdl are same. As long as you do modification (new field etc), and regenerate wsdl -- it will be different
    – kurunve
    Commented Mar 2, 2017 at 15:04
  • 1
    I think you are talking about the Authentication URL. Once you call the login method, it will give you the service URL. I am sure the service URL will be different for production and Sandbox.
    – Saroj Bera
    Commented Mar 2, 2017 at 15:07

1 Answer 1


The ID at the end of the Enterprise WSDL URL is the VersionSet ID.


It encodes the managed package version selections when the enterprise WSDL was generated.

For example, the enterprise WSDL might include components that came from managed packages. Salesforce needs to know which version of the managed package that definition came from to keep everything consistent.

It's likely that they used do differ before the refresh as the Enterprise WSDL was retrieved from both the Sandbox and Production independently and an VersionSet was created for each. Now that the sandbox has been refreshed from production it has access to the same VersionSet. You can probably confirm this by looking at the pod identifier in the 4th and 5th characters of the ID.

See also:

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .