SOAP request returns WSDL file instead of expected data in Postman

Hi everyone,

I’m trying to test a NAVISION 2009 web service using SOAP in Postman. When I send the request, I receive a 200 OK response, but instead of the expected data, the response contains the WSDL file.
Here’s what I’ve done so far:

  1. I’ve set up the NTLM authentication
  2. I’ve set up the SOAP request in Postman with the correct endpoint (I’ve tried two soap body, one of them using wizdler extension)
  3. I’ve included the necessary headers
    Despite this, the response is the WSDL file instead of the actual data. Has anyone encountered this issue before? Am I missing something in the request setup or headers?




Result :

Any guidance or suggestions would be greatly appreciated!

Thanks in advance :blush: :pray:!

Hi @aviation-geologist11,

It sounds like you are doing all the right things.

Normally, when I have an issue with Postman sending Soap requests, I try the same request in SoapUI and If that works, Check the Request, click on Raw tab and check what is being sent to the API, then replicate that in Postman.

I’m encountering a 500 Internal Server Error when using SOAP UI to send a request. The response indicates that the SOAP message is invalid.

HTTP/1.1 500 Internal Server Error
Content-Length: 394
Content-Type: text/xml; charset=utf-8
Server: Microsoft-HTTPAPI/2.0
<s:Envelope xmlns:s=“http://schemas.xmlsoap.org/soap/envelope/”><s:Body><s:Fault>a:System.Net.WebExceptionSoap message is invalid!Soap message is invalid!</s:Fault></s:Body></s:Envelope>

That is interesting as it gives you some response in Postman.

I’m guessing the request body and the header are identical?

any Proxy issues?