Key takeaways
- Status codes, PUT vs PATCH, idempotency and 401 vs 403 come up in almost every QA interview round.
- Postman tests use the pm object with Chai-style assertions; Newman runs the same collection from the command line in CI.
- Every endpoint needs positive, negative, boundary and security checks, not only a 200 response.
- These are original Uncodemy short notes for revision, not official Postman or vendor documentation.
About these API testing notes
This page offers Uncodemy's API testing notes as a free PDF. API testing checks the business logic of an application directly through its requests and responses, without going through the user interface, so it is faster and more stable than UI testing and finds bugs earlier. The notes are written as short points with comparison tables and small worked examples, so a fresher can revise the whole topic in about an hour before an interview.
Please note: these are original Uncodemy revision notes. They are not official documentation from Postman or any other tool vendor. Tool menus and features change between versions, so check the official documentation when something on your screen looks different.
What's inside the API testing notes
The PDF has 8 pages arranged in 9 topic sections, followed by a list of the most asked practice questions and an interview tip. The sections move from concepts to hands-on Postman work, so read them in order the first time. Here is what each section covers.
API basics
What an API is, why API testing sits in the middle of the test pyramid, a table comparing REST, SOAP, GraphQL, gRPC and WebSocket, endpoints and base URLs, and JSON data types with a sample request body.
REST and HTTP methods
The REST constraints such as statelessness, resource naming rules (plural nouns, no verbs, versioning), and a table of GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS marked as safe or idempotent, with query and path parameters and a worked pagination example.
Request and response anatomy
The parts of a request and a response, common headers such as Content-Type, Accept, Authorization, Cache-Control and Cookie, body types from raw JSON to form-data, and why response time and size are part of quality.
HTTP status codes
A full table from 200 to 504 showing when each code is used, the five code classes, and the difference between 401 and 403 in one line.
Authentication and security
Basic auth, API keys, bearer tokens, JWT structure, OAuth 2.0 and session cookies, why Base64 is encoding and not encryption, and a checklist of API security tests linked to the OWASP API Security Top 10.
Postman basics
Workspaces, collections and requests, variable scopes and environments for Dev, QA and Prod, the steps to send a request, and features such as pre-request scripts, the Collection Runner, mock servers, monitors and Newman, plus free practice APIs.
Writing tests in Postman
pm.test and pm.expect examples, a snippet table for status, response time, headers and body values, chaining a login token into later requests, data-driven runs from a CSV file, and running a collection with Newman in Jenkins or GitHub Actions.
What to test and tools
A worked list of checks for a POST /users endpoint, test types from functional and validation to contract and regression, what to verify on every response, and a tool table (Postman, REST Assured, Karate, Python requests with pytest, JMeter, k6, Swagger, SoapUI) with a REST Assured given-when-then line.
REST vs SOAP and good practice
A comparison table, rules for clean test data and keeping secrets in environment variables, a checklist for testing a new API, and what to include in an API bug report.
Most asked questions (practice)
Ten interview-style questions, from defining an API to writing test cases for a POST endpoint, and a closing tip on practising with a public demo API.
How to use these notes to learn API testing
API testing is learnt by sending real requests, so keep Postman open while you read each section.
- Send every HTTP method to a free practice API such as reqres.in or jsonplaceholder and note the status code you get back.
- Recreate the snippet table from section 7 in one Postman request: five tests for status, time, header, body value and a saved variable.
- Build a two-request chain where the login response saves a token and the next request sends it in the Authorization header.
- Export the collection and run it once with Newman from the terminal, so you can explain how it fits into CI.
A simple three-pass method works well with short notes. In the first pass, read one section and underline only what you do not already know. In the second pass, close the notes and write the status code table, method table and test snippets for that section on a blank sheet, then compare and correct in a different colour. In the third pass, a day or two later, answer two or three interview-style API testing questions in timed conditions using only memory. Add your own examples and doubts in the margins so the PDF becomes your personal revision copy.
Tables and definitions to memorise
- Method table: GET is safe and idempotent; POST is neither; PUT and DELETE are idempotent; PATCH is not guaranteed to be.
- Status codes 200, 201, 204, 400, 401, 403, 404, 405, 409, 422, 429, 500 and 503, each with a one-line meaning.
- JWT = header.payload.signature, each part base64url encoded; it is signed, not encrypted, so it must never carry passwords.
- Pagination offset = (page - 1) x limit; page 3 with limit 20 skips 40 records and returns records 41 to 60.
- Postman variable scopes (global, collection, environment, data, local) and the double curly brace syntax for using them.
Common mistakes that cost you in interviews
- Checking only the status code and not the body fields, data types, headers and response time.
- Mixing up 401 (not authenticated) and 403 (authenticated but not allowed).
- Saying PUT and PATCH are the same; PUT replaces the full resource, PATCH changes only part of it.
- Hard-coding tokens and base URLs inside requests instead of using environment variables.
- Testing against production data or pasting real secrets into a shared collection.
Interview focus: API testing topics asked most
In QA and backend fresher interviews, API questions usually start with HTTP basics and then move to a hands-on Postman task.
- HTTP methods, idempotency and PUT vs PATCH.
- Status codes, and authentication vs authorisation.
- Postman variables, tests, request chaining and Newman.
- Writing positive and negative test cases for one endpoint.
Typical interview questions
- What is an API, and why do we test APIs separately from the UI?
- Explain the REST principles and compare REST with SOAP.
- What is the difference between PUT and PATCH? What is idempotency?
- Explain status codes 200, 201, 204, 400, 401, 403, 404 and 500.
- How do you use variables and write tests in Postman?
- How do you chain a login request with a get-profile request?
- Write test cases for a POST /users API.
Questions and their depth differ between companies and roles. In a hands-on round, explain one API you tested end to end: the endpoint, the cases you wrote, one bug you found and how you reported it with the request, the actual response and the expected response.
A 7-day revision plan for API testing
- Day 1: API basics, REST and HTTP methods.
- Day 2: Request and response anatomy, HTTP status codes.
- Day 3: Authentication and security.
- Day 4: Postman basics: build a collection with environments for two servers.
- Day 5: Writing tests in Postman, chaining requests and a Newman run.
- Day 6: What to test and tools, REST vs SOAP: write a full set of positive and negative cases for POST /users and automate them.
- Day 7: answer the most asked practice questions at the end of the notes aloud, two minutes each, then explain your collection to a friend as if it were an interview.
Keep the status code and method tables on one sheet for the last hour before an interview, and do not start a new tool on the final day.
Who these notes are for
- Manual testers who want to move into API and backend testing.
- QA and backend freshers preparing for software testing interviews.
- B.Tech, BCA and MCA students learning software testing or web services.
- Developers who want a quick checklist for testing their own REST APIs.
The notes are a revision aid, not a full course. If a topic is new to you, practise it in Postman first and then use the notes to revise. For interview practice, pair them with the API testing interview questions page, and use the Postman API testing guide for step-by-step screens. To learn API, manual and automation testing with a trainer, see the Software Testing course.
Download API Testing Notes PDF
API Testing Notes PDF: Postman and REST
The PDF carries the same content as this page in a clean, print-ready layout, so you can read it offline and keep it for revision.
8 pages · 100 KB · PDF · Updated 5 Nov 2026