Skip to content
CodeKruPro

Organize your first Postman collection

Automation taskEasyAsked in: Capgemini, Infosys

"Have you used Postman? How do you organize your requests?" Build and organize a collection here, so your answer comes from practice.

Organize your first Postman collection

02 · Build reusable requests and investigate results

Recommended first: Distinguish request Content-Type from response preferences

Your goal: Organize your first Postman collection

Type each request yourself. This lesson shows the method, URL, headers and body. It does not fill the console.

  1. 1Send requests
  2. 2Submit answers

Start here: sign in to practise.

Jump to practice

What you will learn

You have sent individual requests. Postman can save them together in a collection, like a labelled folder of experiments. Now create that folder yourself; the course console and Postman are separate clients.

Your goals

  • Create and organize an actual Postman collection.
  • Export its structure and keep separate positive and negative response evidence.

Before you start

Read the previous lesson first if you have not already. This course does not require programming.

Practice setup

These requests use the public TestKru teaching API. No workspace is needed unless a step says so. Leave the body empty for GET, HEAD and OPTIONS. Example people and emails are fictional. Changes to /api/users are simulated and are not saved.

Follow these steps

  1. Install/open Postman using the linked quick start. Create a collection named Beginner API Lab. Add folders named Users and Products. No programming is needed.
  2. In Users, save GET https://testkru.com/api/users/1 and GET https://testkru.com/api/users/99. In Products, save GET https://testkru.com/api/products/1. Leave bodies empty and choose No Auth.
  3. Send all three in Postman. Inspect each response, then name each saved request for the resource and the result you observed. Save your changes.
  4. Send the same three requests in the course console and select each response. These console logs are the verifiable execution evidence; a collection export alone cannot prove execution.
  5. Export Beginner API Lab as Collection v2.1 JSON from the collection menu. Open the file in a text editor, paste its contents in the collection answer, and submit. Keep this collection for the next lesson.

Investigate before concluding

First record the actual result for each case. Compare the body, headers and later state with the stated contract. Keep an observation separate from a prediction; use the model answer only after making your own attempt.

What to keep as evidence

  • Positive and negative requests are both sent.
  • The name states the expected result.
  • Another person could find the negative request from the name alone.
References for this lesson

Finish this assignment

Select each named response with Use this response. Answer from those responses or the transcript on this page. Click Submit Answers. Your score is the percentage of checks that passed. Core checks are required to finish. Extra evidence checks are labelled. A saved 100/100 means every check passed. Continue opens the next lesson you can submit.

If something goes wrong
  • Change one part of the request at a time. If a check needs attention, read the note under it and compare it with the response you selected.
Self-review and independent variation
  • Positive and negative requests are both sent.
  • The name states the expected result.
  • Another person could find the negative request from the name alone.

Add a missing-product request and give it the same kind of name.

Automatic checks verify the requests and answers configured for this lesson. The self-review is for your own reasoning. A score is not a certificate.

Open API reference

Practise and save your evidence

The lesson is public. Sign in to send requests and save progress. You will return to this lesson.

Sign in to practiseCreate an account