Building Your First GET Request
To send your first request, open a new tab in Postman, leave the method dropdown on its default value of GET, and type a URL such as https://api.postman-echo.com/get into the address bar — a public sandbox endpoint Postman itself hosts specifically for practicing requests. Clicking the blue Send button triggers Postman to open a connection, transmit the request, and wait for a reply, after which the response panel at the bottom populates automatically. There is no need to configure headers or a body for a basic GET request against a public endpoint like this one; the method and URL alone are enough to get a valid response.
Cricket analogy: It's like a debutant facing his very first ball in international cricket against a gentle net bowler rather than a fast bowler — a first GET request against a safe sandbox endpoint like postman-echo.com is a low-stakes first delivery to build confidence.
Reading the Response
Once the response arrives, the status line above the response body shows three key facts at a glance: the HTTP status code (200 OK for success), the time taken in milliseconds, and the response size in bytes or kilobytes. The Body tab, in its default Pretty view, displays the JSON payload with syntax highlighting and collapsible objects and arrays, letting you drill into nested fields by clicking the small arrows next to each key. If the request failed, the status code alone often tells you why — a 404 means the URL path doesn't exist, a 401 means authentication is missing, and a 500 means the server itself encountered an error.
Cricket analogy: It's like glancing at the scoreboard to instantly know runs, overs, and wickets without watching every ball — the status line gives you code, time, and size at a glance without reading the whole response body.
Saving the Request
A request typed into an unsaved tab disappears once the tab is closed unless it's saved into a collection. Clicking the Save button, or pressing Ctrl+S (Cmd+S on Mac), opens a dialog asking for a request name and which collection (or folder within a collection) to save it into; choosing 'Create Collection' here is how most people create their very first collection. Once saved, the request appears permanently in the sidebar under that collection, and any future edits to the URL, headers, or body are saved back to that same request rather than creating a new one, unless you explicitly use 'Save As' to create a copy.
Cricket analogy: It's like a promising net session that only counts if the coach logs it in the player's development file, otherwise it's forgotten by next week — saving a request into a collection is what makes it count for future reuse.
Postman auto-saves your work-in-progress in an unsaved tab across app restarts on desktop, so accidentally closing the app won't immediately lose your draft. However, explicitly saving to a collection is still the only way to make a request permanently reusable, shareable with teammates, and included in automated Newman runs.
Clicking Send on a GET request with unsaved edits does not save those edits. It's easy to tweak a URL, test it successfully, then close the tab believing the change is preserved — always explicitly save after making a change you want to keep.
# Equivalent curl command for reference, showing what Postman builds and sends for you:
curl -X GET "https://api.postman-echo.com/get?userId=42" \
-H "Accept: application/json"- A first request needs only a method (GET) and a URL — no headers or body required for a public sandbox endpoint.
- postman-echo.com is Postman's official public sandbox for safely practicing requests.
- The response status line shows status code, response time, and payload size at a glance.
- A 200 means success, 404 means the path doesn't exist, 401 means missing authentication, 500 means a server error.
- Requests must be explicitly saved into a collection (Ctrl+S / Cmd+S) to persist and be reused later.
- Editing a saved request and sending again overwrites that same request unless you use Save As.
- Unsaved tab drafts persist across desktop app restarts, but only saving to a collection makes a request shareable and runnable via Newman.
Practice what you learned
1. What is the minimum required to send a basic GET request in Postman?
2. What does postman-echo.com provide?
3. What does a 404 status code indicate?
4. What is required to make a request permanently reusable and shareable with teammates?
5. What happens when you edit a saved request's URL and send it again without using Save As?
Was this page helpful?
You May Also Like
What Is Postman?
An introduction to Postman as an API platform for building, testing, and documenting HTTP APIs, and why it has become the standard tool for API development.
The Postman Interface
A tour of Postman's main workspace layout — sidebar, request builder, response viewer, and console — and how each panel supports the request-response workflow.
HTTP Methods in Postman
How to use GET, POST, PUT, PATCH, and DELETE requests in Postman, including when each method applies and how to attach a request body.