Postman collection organization in Rest API - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Postman collection named "My API".

Rest API

pm.collection.create({ name: "[1]" });

Drag options to blanks, or click blank then click option'

ASample Collection

BAPI Test

CMy API

DTest Suite

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different collection name than specified.

Forgetting to put the name in quotes.

The collection name should be "My API" as specified.

2fill in blank

medium

Complete the code to add a request named "Get Users" to the collection.

Rest API

pm.collection.items.add({ name: "[1]", request: { url: "https://api.example.com/users", method: "GET" } });

Drag options to blanks, or click blank then click option'

AGet Users

BUsers List

CFetch Users

DRetrieve Users

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different request name.

Not matching the case exactly.

The request name should be exactly "Get Users" to match the instruction.

3fill in blank

hard

Fix the error in the code to set the request method to POST.

Rest API

pm.collection.items.add({ name: "Create User", request: { url: "https://api.example.com/users", method: "[1]" } });

Drag options to blanks, or click blank then click option'

APOST

BPUT

CDELETE

DGET

Attempts:

3 left

💡 Hint

Common Mistakes

Using GET or PUT instead of POST.

Using lowercase method names.

The method should be "POST" to create a new user.

4fill in blank

hard

Fill both blanks to add a folder named "User Operations" and add a request named "Delete User" inside it.

Rest API

const folder = pm.collection.items.add({ name: "[1]", item: [] });
folder.items.add({ name: "[2]", request: { url: "https://api.example.com/users/123", method: "DELETE" } });

Drag options to blanks, or click blank then click option'

AUser Operations

BUser Actions

CDelete User

DRemove User

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping folder and request names.

Using incorrect names.

The folder name is "User Operations" and the request name is "Delete User" as specified.

5fill in blank

hard

Fill the blanks to create a request with a JSON body and add it to the collection.

Rest API

pm.collection.items.add({ name: "[1]", request: { url: "https://api.example.com/users", method: "POST", header: [{ key: "Content-Type", value: "[2]" }], body: { mode: "raw", raw: JSON.stringify({ name: "John" }) } } });

Drag options to blanks, or click blank then click option'

ACreate User

Bapplication/json

Capplication/xml

DAdd User

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong Content-Type header.

Not stringifying the JSON body.

The request name is "Create User", the Content-Type header should be "application/json" for JSON data, and the body mode is "raw" with JSON stringified data.

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