API Testing for Quality Assurance (QA)s
API testing checks the service layer directly by sending HTTP requests and asserting on status codes, headers and response bodies, without going through the UI. Postman and code-based libraries like REST-assured cover it, and mocks and managed test data make the tests fast and repeatable.
Stage: Test Automation · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in API Testing
- Send GET, POST, PUT and DELETE requests in Postman and read the responses
- Assert on status code, JSON fields and response time
- Chain requests by passing a token or id from one to the next
- Validate a response against a JSON schema
- Mock a slow or unavailable dependency with a stub server
- Create and clean up test data through the API
API Testing interview questions
What would you check in a REST API response?
Check the status code, response headers such as content type, the body fields and types against the contract, error messages for bad input, and the response time. Also confirm that side effects, like a created record, actually exist afterwards.
Why mock a dependency in an API test?
A mock makes a third-party service predictable, fast and free to call. It lets you force error responses and timeouts that are hard to trigger for real, and it keeps your tests from failing when someone else's system is down.
Where API Testing fits in the Quality Assurance (QA) roadmap
API Testing belongs to the Test Automation stage (beginner level), which takes about 9 hours. Reliable, maintainable checks.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap