API Response Test with Postman

The very first thing to note is the status code at the top right. "200" means successful processing of the API request. The most interesting information in the body is certainly the "localdmid" (for Xelon the main identification of a server), as well as, for example, the IP address at the bottom (made unrecognisable).

Checking values in JSON

I can now define in Postman which information is used to recognise whether a request was successful. In our case, we check whether the localvmid exists:

pm.test("Check if localvmid exists", function () {
    var jsonData = pm.response.json();
    pm.expect(jsonData.device.localvmid).to.be.a("string");
});

The command searches the JSON structure in the body for the localvmid value within "Device". A string is expected. If the answer does not contain a string, the test fails and alerts the developer team via Postman Monitoring.

Reuse values as variables for the API response test with Postman

If a collection is used for monitoring, for example, it is possible that certain JSON returns must be used again in one of the subsequent API requests. For example, if we create a server and then want to check the server status in another call, we need this ID. We can now easily read the localvmid from the return and save it as a variable:

var jsonData = JSON.parse(responseBody);
pm.environment.set("LOCALVMID", jsonData.device.localvmid);
console.log(pm.environment.get("LOCALVMID"))

The localvmid is read out and stored in the environment variable "localvmid". I can now use this variable in the next request.

The complete "Tests" section now looks like this: