Reading about Postman is not the same as using Postman. This lesson is all hands-on. Open Postman and complete every exercise below. No shortcuts — the muscle memory matters.
Create a collection called "TesterRank — API Practice" with the following structure and requests. Save every request with a descriptive name.
TesterRank — API Practice/
Variables:
baseUrl = https://jsonplaceholder.typicode.com
Posts/
List All Posts GET {{baseUrl}}/posts
Get Single Post GET {{baseUrl}}/posts/:id (id = 1)
Get Posts by User GET {{baseUrl}}/posts?userId=1
Create New Post POST {{baseUrl}}/posts (with JSON body)
Full Update Post PUT {{baseUrl}}/posts/:id (id = 1, full body)
Partial Update Post PATCH {{baseUrl}}/posts/:id (id = 1, title only)
Delete Post DELETE {{baseUrl}}/posts/:id (id = 1)
Users/
List All Users GET {{baseUrl}}/users
Get Single User GET {{baseUrl}}/users/:id (id = 3)
Create New User POST {{baseUrl}}/users (with JSON body)
Comments/
Get Comments for Post GET {{baseUrl}}/posts/:postId/comments (postId = 1)
Get Comments by Email GET {{baseUrl}}/comments?email=Eliseo@gardner.bizPOST {{baseUrl}}/posts — body: { "title": "Test Post", "body": "Created by me", "userId": 1 }. Note the returned id.
GET {{baseUrl}}/posts/101 — Read the post you just created (use the id from step 1)
PUT {{baseUrl}}/posts/101 — Replace with: { "id": 101, "title": "Replaced Post", "body": "All new content", "userId": 1 }
PATCH {{baseUrl}}/posts/101 — Partially update: { "title": "Only Title Changed" }
DELETE {{baseUrl}}/posts/101 — Delete it. Note the status code.
GET {{baseUrl}}/posts/101 — What do you get back?
For each request, write down: status code, response time, number of fields in response
Send GET {{baseUrl}}/posts/1 and answer these questions by inspecting the response:
Using the Params tab (not typing in the URL), test these queries:
Open the Banking Portal (link below) in your browser
Open DevTools (F12) > Network tab > filter by Fetch/XHR
Interact with the portal — login, check balances, transfer money
For each API call you see, note: URL, method, status, response body
Now recreate those SAME calls in Postman manually
Compare — did you get the same response? Same status code?
This "inspect in DevTools, recreate in Postman" workflow is exactly what senior testers do in real projects. You intercept real API calls, reproduce them in Postman, and then modify them to test edge cases.
Don't skip these exercises. API testing is a hands-on skill. Reading about it is like reading about swimming — you won't learn until you jump in the pool. Spend the 15 minutes. It'll make the rest of this course 10x easier.
Key Point: Practice every concept hands-on. Build the collection, complete the CRUD cycle, inspect headers, test query params. Muscle memory is everything.