Postman for Beginners: A Step-by-Step API Testing Tutorial

You’ve just joined a project. The developer says, “The API is ready. Can you test it?” You nod. Then you open your laptop and wonder where to even start.

If that sounds familiar, you’re in good company. API testing looks scary because there’s no screen to click. But with a free tool called Postman, it becomes simple. You send a request, read the answer and check that it’s right.

In this Postman tutorial for beginners, you’ll send your first request, read the response, use variables, write a basic test and run a whole collection. You don’t need to code much. You only need about 30 minutes. By the end of this Postman for beginners guide, you will have a working collection.

What is API testing? A Postman for beginners primer

An API is a way for two systems to talk. Think of a waiter in a restaurant. You (the app) tell the waiter (the API) what you want. The waiter goes to the kitchen (the server) and brings back your food (the data).

API testing means checking that waiter. Did the right request get the right answer? Was it fast enough? What happens when you ask for something that doesn’t exist?

Postman is a tool that lets you play the customer. You write the order, press Send and look at what comes back. If you’d like a quick overview of the tools testers use, read Top 10 Software Testing Tools.

Before you start

• Install the free Postman desktop app, or use Postman in your browser.
• Use a practice API so you can’t break anything. In this tutorial we use JSONPlaceholder, a free fake API made for learning.
• Create a free Postman account if the app asks you to sign in.

Step 1: Send your first GET request

A GET request asks for data. It’s the simplest request, so we start here.

1. Open Postman and click New, then choose HTTP request.
2. Keep the method as GET.
3. Paste this address in the URL box: https://jsonplaceholder.typicode.com/posts/1
4. Click Send.

In a second or two, you’ll see the answer in the lower half of the screen. That’s your first API test.

Step 2: Read the response

Beginners often look only at the data. Testers look at three things. You can look up every code in the MDN list of HTTP status codes.

• Status code. You should see 200 OK. It means the request worked. A 404 means not found. A 500 means the server had a problem.
• Response time. Postman shows it in milliseconds. A slow answer can be a bug too.
• Body. Choose the Pretty view. You’ll see a small piece of JSON with fields such as userId, id, title and body.

Takeaway: a good test checks the code, the time and the data, not just the data.

Step 3: Try the other HTTP methods

Real apps do more than read. They create, change and delete. Each action has its own method. For a full reference, see the MDN guide to HTTP request methods.

Method	What it does	Example
GET	Reads data	Get post number 1
POST	Creates data	Add a new post
PUT	Replaces data	Update post number 1
PATCH	Changes part of the data	Change only the title
DELETE	Removes data	Delete post number 1

To try a POST request, change the method to POST and use the address https://jsonplaceholder.typicode.com/posts. Open the Body tab, choose raw, set the type to JSON and paste this:

{
  "title": "My first post",
  "body": "Testing with Postman",
  "userId": 1
}

Click Send. This practice API answers with 201 Created and gives your new post an id. JSONPlaceholder doesn’t really save it, but the reply shows how a real API would behave.

Step 4: Use parameters and headers

Parameters filter the data. Headers carry extra information, such as the type of data you send or a login token.

• Open the Params tab and add the key userId with the value 1. Use the address https://jsonplaceholder.typicode.com/posts. Postman builds the full address for you and returns only the posts for that user.
• Open the Headers tab to see what Postman sends by default. Add your own header only when the API asks for one.

Step 5: Save requests in a collection

Typing the same address again and again gets boring. A collection is a folder where you keep related requests together.

1. Click Save on your request.
2. Create a new collection called “Practice API”.
3. Save your GET and POST requests inside it, with clear names such as “Get post 1” and “Create post”.

Good names matter. In three weeks, you won’t remember what “Request 7” was.

Step 6: Use variables so you don’t repeat yourself

Right now the base address is typed in every request. If it changes, you’d fix it everywhere. Variables solve that.

1. Create an Environment and name it “Practice”.
2. Add a variable called baseUrl with the value https://jsonplaceholder.typicode.com.
3. Select that environment at the top right.
4. In your requests, write the address as {{baseUrl}}/posts/1.

Now one change updates every request. Teams use the same idea to switch between test and production servers.

Step 7: Write your first test

So far you checked results with your eyes. Postman can check them for you. Open the Tests tab of your GET request and paste:

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

pm.test("Post id is 1", function () {
  var data = pm.response.json();
  pm.expect(data.id).to.eql(1);
});

Click Send again and open the Test Results tab. You should see two green passes. If you change the expected id to 2, one test turns red. That’s how you know your test works.

You don’t need to learn JavaScript first. Copy small examples like this and change the numbers and field names. Confidence comes from using them.

Step 8: Run the whole collection

Click the three dots next to your collection and choose Run collection. Postman runs every request in order and shows which tests passed. This is a simple way to build a quick check you can repeat before each release. When you’re ready for larger suites, read Introduction to Automation Frameworks.

Common Postman mistakes beginners make

• Testing only the happy path. Also send wrong or empty data and see if the API answers with a clear error.
• Checking only the status code. A 200 with the wrong data is still a bug.
• Forgetting to select the environment, then wondering why {{baseUrl}} doesn’t work.
• Leaving real passwords or tokens inside shared collections. Keep secrets in environment variables.

Your 7-day Postman for beginners action plan

1. Install Postman and send the GET request from Step 1.
2. Try POST, PUT and DELETE on the practice API.
3. Save everything in a collection with clear names.
4. Add one variable and two tests.
5. Next time, test a small API from your own project. Ask your developer for a test environment first.

Conclusion

API testing isn’t magic. You send a request, read the reply and check it against what you expect. This Postman API testing tutorial gives you a base you can build on. New to the tool? The official Postman Learning Center has extra guides to keep learning.

Postman just makes that loop quick and visible. Start small, save your work and add one test at a time.

In a week, you’ll wonder why it looked so hard.

Call to action

Pick one step from this guide and try it today. Then watch the full Postman for Beginners video on our channel. If you want to write better test ideas to put into Postman, read How to Write Effective Test Cases. For a wider view of testing with AI, see my books. Share your first Postman for beginners result with a teammate and ask for feedback.

FAQs

Related articles

• Introduction to Automation Frameworks: Building a Robust Test Suite
• How to Manage Scope Changes Without Compromising Software Quality: A Project Manager’s Guide
• How to Write Test Cases with ChatGPT: Step by Step