If you are using Postman, at first you must export as cURL: How to export Postman request as a cURL command to help MuleSoft Support
In Mule, we need to enable the HTTP wire logging to see the request and response: How to Enable HTTP Wire Logging for the HTTP Connector
On the first line of the log, we can see:
-Method
-Endpoint
-HTTP protocol
In the following lines the headers with the values.
After headers, the body.
The same structure applies for the response.
You will see something like this:
In Mule, you can see the same in the logs.
We are now able to check if the requests are equals by comparing the requests.
Using -v parameter in the cURL command, we enable verbose mode
Find the HTTP Wire Logging at the mule EE log, the API log or the Studio console
In this case, the header "Postman-Token" was generated on Postman and it is not needed and the header "Name" is different between requests. (The response is good on both cases because is a dummy API REST)
001116956

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.