Postman collection organization in Rest API - Mini Project: Build & Apply

Organize a Postman Collection for API Testing

📖 Scenario: You are working as a junior API tester. Your team uses Postman to test APIs. Currently, the Postman collection is messy with all requests in one folder. You want to organize the collection by grouping requests into folders based on their API resource type.

🎯 Goal: Create a Postman collection JSON structure with organized folders. Each folder groups related API requests. This helps your team find and run tests easily.

📋 What You'll Learn

Create a Postman collection JSON with a info section containing name and schema

Add two folders named Users and Products inside the item array

Add one GET request named Get User inside the Users folder with the URL https://api.example.com/users/1

Add one GET request named Get Product inside the Products folder with the URL https://api.example.com/products/1

💡 Why This Matters

🌍 Real World

Organizing Postman collections helps teams manage and run API tests efficiently, especially when APIs grow larger.

💼 Career

API testers, developers, and QA engineers often organize Postman collections to improve collaboration and testing workflows.

1

Create the basic Postman collection structure

Create a JSON object called collection with an info section. The info section must have name set to My API Tests and schema set to https://schema.getpostman.com/json/collection/v2.1.0/collection.json. Also add an empty item array to hold folders.

Rest API

{
  "info": {
    "name": "My API Tests",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
  },
  "item": [
    // Your code here
  ]
}

Hint

Start by creating the main JSON object with info and an empty item array.

2

Add folders for Users and Products

Add two folders inside the item array of collection. Each folder is an object with a name and an empty item array. The first folder's name is Users and the second folder's name is Products.

Rest API

{
  "info": {
    "name": "My API Tests",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
  },
  "item": [
    // Add Users and Products folders here
  ]
}

Hint

Folders are objects inside the item array with their own name and item arrays.

3

Add a GET request to the Users folder

Inside the Users folder's item array, add a GET request object. The request should have name set to Get User and a request object with method set to GET and url set to https://api.example.com/users/1.

Rest API

{
  "info": {
    "name": "My API Tests",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
  },
  "item": [
    {
      "name": "Users",
      "item": [
        // Add Get User request here
      ]
    },
    {
      "name": "Products",
      "item": []
    }
  ]
}

Hint

Requests go inside the folder's item array as objects with name and request details.

4

Add a GET request to the Products folder

Inside the Products folder's item array, add a GET request object. The request should have name set to Get Product and a request object with method set to GET and url set to https://api.example.com/products/1.

Rest API

{
  "info": {
    "name": "My API Tests",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
  },
  "item": [
    {
      "name": "Users",
      "item": [
        {
          "name": "Get User",
          "request": {
            "method": "GET",
            "url": "https://api.example.com/users/1"
          }
        }
      ]
    },
    {
      "name": "Products",
      "item": [
        // Add Get Product request here
      ]
    }
  ]
}

Hint

Similar to the Users folder, add the request inside the Products folder's item array.

Practice

1. What is the main purpose of organizing requests into folders within a Postman collection?

easy

A. To encrypt the API requests for security

B. To increase the speed of API responses

C. To automatically generate API documentation

D. To group related API requests for easier access and management

Solution

1. Step 1: Understand the role of folders in Postman collections

   Folders help group related API requests logically, making them easier to find and manage.

2. Step 2: Identify the benefit of grouping requests

   Grouping reduces clutter and helps testers quickly locate and run related requests.

3. Final Answer:

   To group related API requests for easier access and management -> Option D

4. Quick Check:

   Folders organize requests = A [OK]

Hint: Folders group related requests for easy management [OK]

Common Mistakes:

• Thinking folders speed up API responses
• Confusing folders with encryption
• Assuming folders auto-generate docs

2. Which of the following is the correct way to add a new folder inside a Postman collection?

easy

A. Click the 'New Request' button directly

B. Right-click the collection and select 'Add Folder'

C. Edit the collection JSON manually to add a folder

D. Drag and drop requests into the collection

Solution

1. Step 1: Recall Postman UI actions for folder creation

   In Postman, you add folders by right-clicking the collection and choosing 'Add Folder'.

2. Step 2: Eliminate incorrect options

   'New Request' adds a request, not a folder; editing JSON is advanced and not typical; drag and drop moves requests but doesn't create folders.

3. Final Answer:

   Right-click the collection and select 'Add Folder' -> Option B

4. Quick Check:

   Add folder via right-click = A [OK]

Hint: Right-click collection to add folder quickly [OK]

Common Mistakes:

• Clicking 'New Request' to add a folder
• Trying to drag requests to create folders
• Editing JSON instead of using UI

3. Given a Postman collection with folders named 'Users', 'Orders', and 'Products', which folder will a request named 'Create Order' most logically belong to?

medium

A. Orders

B. Users

C. Products

D. None of the above

Solution

1. Step 1: Analyze the request name and folder names

   The request 'Create Order' relates to creating an order, so it fits best under the 'Orders' folder.

2. Step 2: Match request purpose to folder

   'Users' relates to user data, 'Products' to product info, so 'Orders' is the logical folder.

3. Final Answer:

   Orders -> Option A

4. Quick Check:

   Request about orders goes to Orders folder = B [OK]

Hint: Match request name topic to folder name [OK]

Common Mistakes:

• Putting 'Create Order' in 'Users' folder
• Choosing 'Products' folder incorrectly
• Selecting 'None of the above' without reason

4. You notice that some requests in your Postman collection are missing descriptions, making it hard for teammates to understand their purpose. What is the best way to fix this?

medium

A. Delete the requests without descriptions

B. Rename the collection to a more descriptive name

C. Add clear descriptions to each request explaining its use

D. Export the collection and edit descriptions in a text editor

Solution

1. Step 1: Identify the problem and best practice

   Missing descriptions cause confusion; adding clear descriptions helps teammates understand requests.

2. Step 2: Evaluate options for fixing the issue

   Renaming collection doesn't fix request descriptions; deleting requests loses work; editing JSON externally is error-prone.

3. Final Answer:

   Add clear descriptions to each request explaining its use -> Option C

4. Quick Check:

   Descriptions clarify requests = C [OK]

Hint: Add descriptions to requests for clarity [OK]

Common Mistakes:

• Renaming collection instead of adding descriptions
• Deleting requests unnecessarily
• Editing JSON outside Postman risking errors

5. You want to organize a large Postman collection with hundreds of API requests for a complex project. Which strategy will best improve maintainability and teamwork?

hard

A. Use nested folders to group requests by feature and add detailed descriptions

B. Keep all requests in one flat list to avoid confusion

C. Create separate collections for each request to isolate them

D. Only use folders without descriptions to save time

Solution

1. Step 1: Consider organization for large collections

   Nested folders help group requests by features or modules, making navigation easier.

2. Step 2: Importance of descriptions for teamwork

   Detailed descriptions explain request purpose, aiding team understanding and future maintenance.

3. Step 3: Evaluate other options

   Flat lists become cluttered; separate collections for each request are inefficient; skipping descriptions reduces clarity.

4. Final Answer:

   Use nested folders to group requests by feature and add detailed descriptions -> Option A

5. Quick Check:

   Nested folders + descriptions = maintainability [OK]

Hint: Group by feature with folders and add descriptions [OK]

Common Mistakes:

• Using one flat list for many requests
• Creating too many separate collections
• Skipping descriptions to save time