Clearly there is a diferencie, because when sending the request using parameters it returns an error message: “{"message":"folderDto must not be null","errorCode":0,"traceId":"00-b26ca4ee01e5a252c0340b5c0f51a18a-b3e1a89fea57ef25-01"}”
And when sending the same request using the Body option in the HTTP Request property, it works.
Parameters: Parameters are visible in the URL itself and are often used for simple data retrieval or filtering.
e.g. http://example.com/api/data?id=123,
the id=123 is the parameter with the key id and the value 123.
Body: body contains data that isn’t visible in the URL and is often used for sending more complex or larger amounts of information. It can contain JSON, XML, form data, or other formats
Clearly there is a diferencie, because when sending the request using parameters it returns an error message: “{“message”:“folderDto must not be null”,“errorCode”:0,“traceId”:“00-b26ca4ee01e5a252c0340b5c0f51a18a-b3e1a89fea57ef25-01”}”
whether it works from parameter or body depends where the developer of the API put the property, if they put it in parameter then you have to send it using paramters, same for body
Parameters correspond to the request parameters that are appended to the request URL
Body is the actual request body (usually it defines the request payload or the data that needs to be processed by the request).
They are different things
What tell to us where pass the information is de API definition that we are working with. The API documentation should says where and how to pass the information
