Bird
Raised Fist0
Postmantesting~15 mins

Example requests and responses in Postman - Build an Automation Script

Choose your learning style10 modes available
Verify GET request to fetch user details
Preconditions (2)
Step 1: Open Postman
Step 2: Create a new GET request
Step 3: Enter URL https://api.example.com/users/123
Step 4: Click Send button
Step 5: Observe the response body and status code
✅ Expected Result: Response status code is 200 and response body contains user details with id 123
Automation Requirements - Postman Tests (JavaScript)
Assertions Needed:
Verify response status code is 200
Verify response body contains user id 123
Verify response body has keys: id, name, email
Best Practices:
Use pm.response.to.have.status for status code assertion
Use pm.expect with JSON parsing for body content
Write clear and simple test scripts inside Postman Tests tab
Automated Solution
Postman
pm.test('Status code is 200', function () {
    pm.response.to.have.status(200);
});

pm.test('Response has user id 123', function () {
    const jsonData = pm.response.json();
    pm.expect(jsonData.id).to.eql(123);
});

pm.test('Response has required keys', function () {
    const jsonData = pm.response.json();
    pm.expect(jsonData).to.have.all.keys('id', 'name', 'email');
});

The first test checks if the response status code is 200, which means the request was successful.

The second test parses the JSON response and verifies the user id is exactly 123.

The third test ensures the response JSON contains the keys 'id', 'name', and 'email', confirming the expected data structure.

All tests use Postman's pm and pm.expect APIs for clear and reliable assertions.

Common Mistakes - 3 Pitfalls
Not parsing response JSON before accessing properties
Checking status code with pm.response.code instead of pm.response.to.have.status
Hardcoding expected values without verifying response structure
Bonus Challenge

Now add tests for POST request to create a new user with 3 different user data inputs

Show Hint

Practice

(1/5)
1. What is the main purpose of example requests and responses in Postman?
easy
A. To design website layouts
B. To create new APIs automatically
C. To write backend server code
D. To show how to use an API step-by-step

Solution

  1. Step 1: Understand the role of example requests

    Example requests demonstrate how to call an API with real data.
  2. Step 2: Understand the role of example responses

    Example responses show what the API returns for those requests.
  3. Final Answer:

    To show how to use an API step-by-step -> Option D
  4. Quick Check:

    Example requests + responses = API usage guide [OK]
Hint: Examples explain API use clearly and simply [OK]
Common Mistakes:
  • Thinking examples create APIs
  • Confusing examples with coding
  • Assuming examples design UI
2. Which of the following is the correct way to add an example response in Postman?
easy
A. Change the request method to POST
B. Click 'Save Response' after sending a request
C. Edit the URL in the Params tab
D. Write code in the Tests tab

Solution

  1. Step 1: Identify how to save example responses

    After sending a request, Postman allows saving the response as an example.
  2. Step 2: Confirm the correct action

    Clicking 'Save Response' saves the current response as an example for future reference.
  3. Final Answer:

    Click 'Save Response' after sending a request -> Option B
  4. Quick Check:

    Save response = example response [OK]
Hint: Save response after request to create example [OK]
Common Mistakes:
  • Trying to add examples by editing URL
  • Confusing Tests tab with examples
  • Changing method does not save examples
3. Given this example request in Postman:
{
  "name": "Alice",
  "age": 30
}

And this example response:
{
  "id": 101,
  "name": "Alice",
  "age": 30
}

What does the response show?
medium
A. The API ignores the age field
B. The API returns an error because of missing fields
C. The API returns the user data with a new ID
D. The API returns only the ID

Solution

  1. Step 1: Compare request and response fields

    The request sends name and age; the response adds an id field.
  2. Step 2: Understand the meaning of added id

    The id is usually a unique identifier assigned by the API to the new user.
  3. Final Answer:

    The API returns the user data with a new ID -> Option C
  4. Quick Check:

    Response adds id to request data [OK]
Hint: Response adds new info like ID to request data [OK]
Common Mistakes:
  • Assuming error without error message
  • Ignoring added id field
  • Thinking age is removed
4. You saved an example response in Postman, but it shows outdated data. What is the best way to fix this?
medium
A. Send the request again and save the new response as example
B. Edit the example response manually in the editor
C. Delete the request and create a new one
D. Change the request URL to a different API

Solution

  1. Step 1: Identify how to update example responses

    Example responses reflect saved data; to update, you must get fresh data from the API.
  2. Step 2: Choose the correct update method

    Sending the request again gets current data; saving it updates the example correctly.
  3. Final Answer:

    Send the request again and save the new response as example -> Option A
  4. Quick Check:

    Refresh example by resending and saving response [OK]
Hint: Resend request and save response to update example [OK]
Common Mistakes:
  • Editing example manually can cause errors
  • Deleting request is unnecessary
  • Changing URL changes API, not example
5. You want to create an example request and response in Postman to show how to update a user's email. Which steps should you follow?
hard
A. Send a PUT request with new email, then save the response as example
B. Write the new email in the Tests tab and save the request
C. Change the request method to GET and save the response
D. Delete the user and create a new example request

Solution

  1. Step 1: Use the correct HTTP method for update

    PUT is the standard method to update existing data like email.
  2. Step 2: Save the response after sending the update request

    Saving the response as example shows the API's reply to the update.
  3. Final Answer:

    Send a PUT request with new email, then save the response as example -> Option A
  4. Quick Check:

    Update with PUT + save response example [OK]
Hint: Use PUT for update, then save response example [OK]
Common Mistakes:
  • Using GET instead of PUT for update
  • Editing Tests tab does not create examples
  • Deleting user is unrelated
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard