restman | RESTMan is a browser extension to work on http requests | REST library

Your user parameter in the request is an array of jsons, so you'd need to specify the index to access individual names

It would appear that you have two layers of JSON encoding: One done already by your tools (ASP.NET and Invoke-RestMethod in PowerShell), and one done by yourself manually.

Server side:

1. You have an object containing a key result with value ok.
2. You call JsonSerializer.Serialize on that object, turning it into a string (a JSON string representing the object): {"result":"ok"}
3. You return this string from your request handler method.
4. ASP.NET takes your value and serializes it to JSON (again!), turning it into another string (a JSON string representing another JSON string representing the object): "{\"result\":\"ok\"}"
5. This double-encoded data is sent over the wire and returned in the HTTP request.

Client side:

1. PowerShell receives the raw string "{\"result\":\"ok\"}" from your server.
2. Since the content type is application/json, the Invoke-RestMethod function deserializes it for you, resulting in a new string value {"result":"ok"}, which is the original data returned from your request handler (a JSON string representing your object)
3. You call ConvertFrom-Json on that string, deserializing it a second time, resulting in an object containing a key result and value ok.

You see, if you'd just neither manually serialize nor manually deserialize your data but instead simply return an object and treat $returnData as object too (since your tools on both ends of the wire already take care of that for you anyway), you would end up with the same result, but you'd get the expected once-encoded JSON string over the wire instead of the twice-encoded one you see now.

SoapUI treats the characters ${...} as property expansion.

In order to treat this literally, you will need to provide an extra dollar sign: $${something.

In the future, on the request pane, if you click on "Raw" you will see exactly what was sent.

Try to be more specific, e.g.

That's not an attribute, that's a namespace. Look up xpath & namespaces.

Here is a quick code to atleast find "l7:issuername":

You may have already tried this...setting bodyParser.urlencoded({ extended: true }) and making sure to select x-www-form-urlencoded in Postman. Or selecting raw as the body type, typing in a JSON object for the content in Postman and omitting bodyParser.urlencoded({ extended: true }) altogether.

I follow up you mentioned Document Create Document API, and do a demo to create documentdb document with rest API. You could refer to it. For other operates you could follow the following code and construct the hashed token.

According to the Common Azure Cosmos DB REST request headers, if we want to create a document we need to prepare the Header as following

Solved, the mongoose documentation says :

The first argument is the singular name of the collection your model is for. Mongoose automatically looks for the plural version of your model name. Thus, for the example above, the model Tank is for the tanks collection in the database.

I did not pay attention to this, since my model's name is User, i should have a collection called users, but all I had in my database was User, after creating the 'users' collections, everything worked out.

The JSON file containing the code is invalid JSON.

In a valid JSON file a string value must be surrounded by double quotes ("value") and line breaks must be escaped with \n. Don't use JSON and instead send the code separately or use a JSON encoder which escapes reserved characters.

A syntactically valid JSON file should look somewhat like this: