HomebaseWorks

API testing: practice, test and prove it

Covers HTTP methods, status codes, headers, JSON, REST, authentication, idempotency and negative tests.

FreeNo sign-up to testNo attempts yet

API testing screenings check whether you understand what travels between a client and a server. Typical questions show a request or a JSON response and ask which status code is correct, which header is missing, or what a good negative test would be. Knowing the meaning behind each method and code matters more than any particular tool.

This page uses a generic API client and plain HTTP examples throughout. The lessons explain requests, responses and REST conventions, then how to validate responses and design negative and authentication tests.

Benchmark: The pass mark on this site is 80%, and API testing is commonly screened for QA engineer, automation tester, SDET and backend support roles. Requirements vary by employer.

Lessons

Advertisement

Interview prep

Certificate

Free with an accountA PDF with your name, best score and date. Records this site's tests only.

Common questions

Do I need programming skills for API testing?

You can start with an API client and no code. Automation roles usually also expect scripting in a language such as Java, Python or JavaScript.

Is API testing only about REST?

No, but REST over HTTP with JSON is the most common style in screenings. The same habits of checking status, headers and body apply to other styles.

What is the difference between API testing and UI testing?

API tests call the server directly without a browser, so they are faster and pinpoint server-side problems. UI tests check what a user sees and does on screen.