POST request in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the response status code for this POST request?

Consider this Postman test script snippet that sends a POST request to create a new user. What will be the status code in the response if the user is created successfully?

Postman

pm.test('Status code is 201', function () {
    pm.response.to.have.status(201);
});

A 200

B 404

C 400

D 201

💡 Hint

201 means resource created successfully.

HTTP status code 201 means the POST request successfully created a new resource.

❓ assertion

intermediate

Which assertion correctly verifies the JSON response contains the new user's id?

You send a POST request to create a user. The response JSON contains an 'id' field. Which Postman test assertion correctly checks that the 'id' field exists and is not null?

A pm.expect(pm.response.json().id).to.exist;

B pm.expect(pm.response.json().id).to.be.undefined;

C pm.expect(pm.response.json().id).to.be.null;

D pm.expect(pm.response.json().id).to.equal('');

💡 Hint

The id should exist and not be null or undefined.

Option A correctly asserts that the 'id' field exists in the JSON response.

🧠 Conceptual

advanced

What is the main purpose of using POST requests in API testing?

In API testing, why do we use POST requests instead of GET requests?

A To create new resources or submit data to the server

B To update existing data partially on the server

C To retrieve data from the server without changing it

D To delete resources from the server

💡 Hint

POST is used to send data to the server to create something new.

POST requests are used to create new resources or submit data to the server.

🔧 Debug

advanced

Why does this Postman test fail when checking the response body?

Given this test script after a POST request, why does it fail? pm.test('Response has name', function () { pm.expect(pm.response.text()).to.include('name'); });

A The 'name' field is missing in the response JSON

B pm.expect cannot be used with pm.response.text()

C The response is JSON, so pm.response.text() returns a string, not parsed JSON

D The test syntax is incorrect and missing a semicolon

💡 Hint

Check if the response is parsed JSON or plain text.

pm.response.text() returns the raw response as a string. To check JSON fields, parse it first.

❓ framework

expert

Which Postman test script correctly validates a POST response with nested JSON and status 201?

You send a POST request that returns a JSON response with this structure: { "user": { "id": 123, "profile": { "email": "[e-mail]" } } } Which test script correctly asserts the status is 201 and the email is '[e-mail]'?

A

pm.test('Status and email', () => {
  pm.response.to.have.status(200);
  pm.expect(pm.response.json().user.email).to.eql('[e-mail]');
});

B

pm.test('Status and email', () => {
  pm.response.to.have.status(201);
  pm.expect(pm.response.json().user.profile.email).to.eql('[e-mail]');
});

C

pm.test('Status and email', () => {
  pm.response.to.have.status(201);
  pm.expect(pm.response.json().profile.email).to.eql('[e-mail]');
});

D

pm.test('Status and email', () => {
  pm.response.to.have.status(201);
  pm.expect(pm.response.json().user.profile.email).to.equal('[e-mail]');
});

💡 Hint

Check the JSON path and status code carefully.

Option B correctly checks status 201 and accesses nested email field properly.