PATCH request in Postman - Build an Automation Script

Update user email using PATCH request

Preconditions (2)

Step 1: Open Postman

Step 2: Set request method to PATCH

Step 3: Enter URL https://api.example.com/users/123

Step 4: In the Headers tab, add 'Content-Type' with value 'application/json'

Step 5: In the Body tab, select raw and JSON format

Step 6: Enter JSON payload: {"email": "[e-mail]"}

Step 7: Click Send button

✅ Expected Result: Response status code is 200 OK and response body contains updated email '[e-mail]'

Automation Requirements - Postman Test Scripts

Assertions Needed:

Verify response status code is 200

Verify response body contains updated email '[e-mail]'

Best Practices:

Use environment variables for base URL and user ID

Validate response schema if available

Use descriptive test names

Automated Solution

Postman

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

pm.test('Response has updated email', function () {
    const jsonData = pm.response.json();
    pm.expect(jsonData.email).to.eql('[e-mail]');
});

The first test checks that the server responded with status code 200, meaning the PATCH request was successful.

The second test parses the JSON response body and asserts that the 'email' field matches the updated email we sent.

Using pm.test helps organize tests with clear names. pm.response.to.have.status and pm.expect are Postman assertion methods.

Common Mistakes - 4 Pitfalls

{'mistake': 'Not setting Content-Type header to application/json', 'why_bad': 'Server may reject or misinterpret the request body if content type is missing or incorrect.', 'correct_approach': "Always set 'Content-Type' header to 'application/json' when sending JSON payloads."}

Using PUT instead of PATCH for partial update

Not verifying response status code

Hardcoding URLs and data instead of using variables

Bonus Challenge

Now add data-driven testing with 3 different email inputs to update the user email

Show Hint