Creating collections in Postman

Introduction

Collections help you organize your API requests in one place. They make testing easier and faster.

You want to group related API requests for a project.

You need to share API tests with your team.

You want to run multiple API tests in order automatically.

You want to save your API requests for later use.

You want to document your API endpoints clearly.

Syntax

Postman

1. Open Postman.
2. Click on 'New' button.
3. Select 'Collection'.
4. Enter a name for your collection.
5. (Optional) Add a description.
6. Click 'Create'.

Collections can contain folders to organize requests further.

You can add tests and scripts inside collections for automation.

Examples

This groups all user-related API requests together.

Postman

Create a collection named 'User API Tests'.

Helps others understand the purpose of the collection.

Postman

Create a collection with description 'Tests for payment endpoints'.

Sample Program

This example shows creating a collection and adding a simple GET request. Running the collection executes the request and verifies the API works.

Postman

// Steps to create a collection in Postman
// 1. Click 'New' > 'Collection'
// 2. Name it 'Sample Collection'
// 3. Add a GET request to https://jsonplaceholder.typicode.com/posts
// 4. Save the request inside 'Sample Collection'
// 5. Run the collection to test the request

// Expected result:
// The GET request runs successfully and returns a list of posts with status 200 OK.

Important Notes

You can export collections to share with others.

Use folders inside collections to keep requests organized.

Collections support environment variables for flexible testing.

Summary

Collections group API requests for better organization.

They help automate and share API tests easily.

Creating collections is simple and improves testing workflow.

Practice

1. What is the main purpose of creating a collection in Postman?

easy

A. To group API requests for better organization

B. To write code in Postman

C. To change the API server settings

D. To create user accounts

Solution

1. Step 1: Understand what collections do

   Collections in Postman are used to group API requests together.

2. Step 2: Identify the main benefit

   This grouping helps organize requests and makes testing easier.

3. Final Answer:

   To group API requests for better organization -> Option A

4. Quick Check:

   Collections = Group API requests [OK]

Hint: Collections group requests to keep tests organized [OK]

Common Mistakes:

• Thinking collections are for coding
• Confusing collections with server settings
• Assuming collections create user accounts

2. Which of the following is the correct way to create a new collection in Postman?

easy

A. Go to settings and change the environment

B. Right-click on a request and select 'Delete'

C. Click the 'New' button and select 'Collection'

D. Open the console and type 'create collection'

Solution

1. Step 1: Locate how to create collections

   In Postman, you create collections by clicking the 'New' button.

2. Step 2: Select the correct option

   After clicking 'New', you choose 'Collection' to create one.

3. Final Answer:

   Click the 'New' button and select 'Collection' -> Option C

4. Quick Check:

   Create collection = New button > Collection [OK]

Hint: Use 'New' button to start creating collections [OK]

Common Mistakes:

• Trying to delete requests to create collections
• Changing environment instead of creating collections
• Typing commands in console to create collections

3. Consider this scenario: You create a collection named 'User APIs' and add three requests to it. What will you see in the Postman sidebar?

medium

A. A folder named 'User APIs' containing the three requests

B. Three separate collections named after each request

C. Only one request visible without any collection

D. An error message about duplicate requests

Solution

1. Step 1: Understand collection structure

   A collection acts like a folder holding multiple requests.

2. Step 2: Visualize sidebar display

   The sidebar shows the collection name with its requests nested inside.

3. Final Answer:

   A folder named 'User APIs' containing the three requests -> Option A

4. Quick Check:

   Collection = Folder with requests inside [OK]

Hint: Collections appear as folders with requests inside [OK]

Common Mistakes:

• Thinking each request becomes its own collection
• Expecting requests to appear without collections
• Assuming errors occur when adding multiple requests

4. You tried to add a request to a collection but it did not appear inside. What is the most likely mistake?

medium

A. You created a new collection instead of adding to existing one

B. You forgot to save the request after adding it to the collection

C. You closed Postman before adding the request

D. You changed the environment instead of adding the request

Solution

1. Step 1: Check the process of adding requests

   After adding a request to a collection, you must save it to confirm.

2. Step 2: Identify common user error

   Forgetting to save means the request won't appear in the collection.

3. Final Answer:

   You forgot to save the request after adding it to the collection -> Option B

4. Quick Check:

   Save request after adding = request appears [OK]

Hint: Always save requests after adding to collections [OK]

Common Mistakes:

• Assuming creating new collection adds request automatically
• Closing app before saving changes
• Mixing environment changes with request additions

5. You want to share a set of API tests with your team using Postman collections. Which steps should you follow to create and share the collection properly?

hard

A. Export environment variables only without collections

B. Create individual requests without collections and email each request

C. Change the workspace settings to public without creating collections

D. Create a collection, add requests, save it, then use the 'Share' option to send a link

Solution

1. Step 1: Create and organize requests in a collection

   First, create a collection and add all relevant API requests to it.

2. Step 2: Save the collection and use sharing features

   Save the collection and then use Postman's 'Share' option to generate a link or invite team members.

3. Final Answer:

   Create a collection, add requests, save it, then use the 'Share' option to send a link -> Option D

4. Quick Check:

   Share collections by saving and using Share link [OK]

Hint: Save collections and use Share link to share with team [OK]

Common Mistakes:

• Sharing requests individually instead of collections
• Only exporting environment variables
• Changing workspace without creating collections