When sending a SOAP request from a third-party application to the Salesforce SOAP API, you may receive the following error response:No operation available for request {urn:enterprise.soap.sforce.com}
This error indicates that the SOAP request is being sent to an API endpoint URL that does not match the WSDL (Web Services Description Language) type that was used during authentication. Salesforce provides two primary SOAP API WSDL types — the Enterprise WSDL and the Partner WSDL — and each uses a different endpoint URL path. Sending API requests to the wrong endpoint for the WSDL type used at login causes this error.
Example Scenario
A third-party integration authenticates against Salesforce using the Enterprise WSDL. After login, the integration sends subsequent API requests (such as query or upsert calls) to the Partner WSDL endpoint URL (/services/Soap/u/XX.0) instead of the Enterprise WSDL endpoint URL (/services/Soap/c/XX.0). Salesforce receives the request at the Partner WSDL endpoint but the request format matches the Enterprise WSDL, causing the "No operation available" error.
Salesforce SOAP API uses different URL endpoint paths depending on which WSDL you are using:
/services/Soap/u/XX.0 (the path contains the letter "u")/services/Soap/c/XX.0 (the path contains the letter "c")If you authenticate using one WSDL type but then send subsequent API calls to the endpoint URL of the other WSDL type, Salesforce cannot process the request because the SOAP message structure does not match the expected format at that endpoint.
Ensure that all API calls in your integration — including the initial login call and all subsequent API calls — use the endpoint URL that corresponds to the WSDL you have chosen to use.
/services/Soap/u/XX.0 endpoint pattern./services/Soap/c/XX.0 endpoint pattern.After a successful login, the Salesforce SOAP API login response includes a serverUrl field. Use this serverUrl value (not a hardcoded URL) for all subsequent API calls in your session. This ensures the endpoint URL is always correct and matches the WSDL type used for login.
000387772

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.