Lesson 1 of 14Beginner
What is an API? (In Plain English)
The restaurant analogy
Imagine a restaurant. You (the customer) don't walk into the kitchen — you tell the waiter what you want, and they bring it back from the kitchen. An API (Application Programming Interface) is the waiter: it takes your request, passes it to the system, and brings back a response.
In software, the app you see (front-end) asks an API for data, and the API talks to the server/database and returns it.
Why test the API directly?
- It's faster and more stable than clicking through screens.
- You test the logic without the distraction of the user interface.
- You can catch problems before the front-end is even finished.
Request and response
Every interaction has two halves:
- Request — what you ask for (a method + an address + maybe data).
- Response — what you get back (a status code + data).
That's the whole game. Postman is simply a friendly tool for sending requests and inspecting responses.
Key takeaways
- An API is a messenger that carries requests to a system and responses back.
- Testing the API is faster, more stable and earlier than testing the UI.
- Everything is a request in and a response out.