This collection was built as part of Section 6 – Express: Let's Start Building the Natours API, a hands-on module focused on learning the fundamentals of Express.js by constructing a real-world REST API.
\nThe requests in this collection explore the core building blocks of an Express server and a tours-based API:
\nBasic Express responses – Sending plain text and JSON data from a local Express server (127.0.0.1:3000), demonstrating how Express handles different response types.
POST request handling – Submitting message text to the local server to practice reading request bodies.
\nTours API (local) – Fetching all tours from the locally running Natours API (/api/v1/tours), mirroring the endpoint being built during the course.
Tours API (production) – Querying the live Natours production server (natours.dev) to retrieve all tours and search for a specific tour by its ID.
Authentication boundary – A deliberate failing request to the /api/v1/users endpoint to observe how protected routes behave.
External API example – A call to the Dog CEO API to illustrate how Postman can interact with any third-party REST API.
\nFetches a random dog image URL from the Dog CEO API.
\nEndpoint: GET https://dog.ceo/api/breeds/image/random
Authentication: None required.
\nResponse:\nReturns a JSON object with the following fields:
\nmessage (string): A URL pointing to a random dog image.status (string): The status of the request (e.g., \"success\").Example Response:
\n{\n \"message\": \"https://images.dog.ceo/breeds/hound-afghan/n02088094_1003.jpg\",\n \"status\": \"success\"\n}\nNotes:
\nSends a simple GET request to the root endpoint of a local Node.js/Express development server and retrieves a plain text response.
This request targets the root (/) route of a locally running Express server on port 3000. It expects the server to respond with a plain text message — typically used to verify that the server is up and running correctly.
127.0.0.1:3000 before sending.text/plain.Sends a POST request to the root endpoint of a local Node.js/Express development server to submit a plain text message body.
This request targets the root (/) route of a locally running Express server on port 3000. It is used during the course to practice handling POST requests in Express — specifically reading and processing a text message sent in the request body.
127.0.0.1:3000 before sending.Sends a GET request to the local development server running on 127.0.0.1:3000 and retrieves a JSON response.
This request is used during local development and testing of the Natours API, built with Node.js and Express. It serves as a basic connectivity check to confirm the server is running and returning JSON data correctly.
\n127.0.0.1:3000A JSON object or array returned by the Express server.
\n","urlObject":{"port":"3000","host":["127","0","0","1"],"query":[],"variable":[]}},"response":[],"_postman_id":"47a7cd9f-e865-4fb4-9ae8-8691488ed4d1"},{"name":"GET Natour Tour Data","id":"f21e9a9a-c0f7-49a5-ad66-2041526dda9c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://www.natours.dev/api/v1/tours","description":"Retrieves a list of all available tours from the Natours API.
\nGET https://www.natours.dev/api/v1/tours
No authentication required.
\nNo query parameters, path variables, or request body required.
\nReturns a JSON object containing:
\nstatus — \"success\" if the request was successful.results — The number of tours returned.data.tours — An array of tour objects, each containing details such as tour name, duration, difficulty, price, summary, and more.{\n \"status\": \"success\",\n \"results\": 9,\n \"data\": {\n \"tours\": [\n {\n \"name\": \"The Forest Hiker\",\n \"duration\": 5,\n \"difficulty\": \"easy\",\n \"price\": 397,\n \"summary\": \"Breathtaking hike through the Canadian Banff National Park\"\n }\n ]\n }\n}\nRetrieves a single tour from the Natours API using its unique identifier. This endpoint returns the full tour object matching the provided ID.
\nGET https://www.natours.dev/api/v1/tours/5c88fa8cf4afda39709c2955\nReturns the tour object matching the given ID.
\n{\n \"status\": \"success\",\n \"data\": {\n \"tour\": {\n \"_id\": \"5c88fa8cf4afda39709c2955\",\n \"name\": \"The Forest Hiker\",\n \"duration\": 5,\n \"maxGroupSize\": 25,\n \"difficulty\": \"easy\",\n \"price\": 397,\n ...\n }\n }\n}\nReturned when no tour matches the provided ID.
\n{\n \"status\": \"fail\",\n \"message\": \"No tour found with that ID\"\n}\nMethod: GET\nEndpoint: https://www.natours.dev/api/v1/users
This is a negative test case that intentionally attempts to retrieve login data by sending a GET request to the /api/v1/users endpoint. The request is expected to fail, as GET is not the correct HTTP method for authentication/login operations, and this endpoint does not support retrieving login data in this manner.
GET method for login.GET request.The API should respond with an error status (e.g., 404 Not Found, 405 Method Not Allowed, or 400 Bad Request), confirming that login data cannot be accessed through this endpoint and method combination.
Retrieves a list of all available tours from the Natours API.
\nGET 127.0.0.1:3000/api/v1/tours
This endpoint returns all tour records stored in the Natours database. Use it to fetch the complete collection of tours, including details such as tour names, durations, prices, ratings, and other relevant tour information.
\n