Collections - Request Man

Overview

Collections in Request Man allow you to organize your API requests into logical groups. Think of collections as folders that contain related requests, making it easy to manage, share, and execute multiple API calls.

Just like Postman: Request Man's collection system mirrors the familiar interface you know and love!

Collection Features

Create Collections

Organize requests into named collections for different projects or APIs.

Nested Folders

Create folders within collections for deeper organization.

Collection Auth

Set authentication once for entire collection.

Collection Variables

Define variables shared across all requests in collection.

Collection Scripts

Run scripts before/after every request in collection.

Duplicate & Share

Duplicate collections or export to share with team.

Creating Collections

Click "New Collection" Button

In the collections sidebar, click the 📁+ button.

Name Your Collection

Enter a descriptive name:

"User Management API"
"Payment Gateway Tests"
"Authentication Endpoints"

Collection Created

Your new collection appears in the sidebar, ready for requests!

Adding Requests to Collections

Method 1: Save from Request Builder

Configure Your Request

Set up URL, method, headers, body, etc.

Click Save Button

Click the "Save" button in the request builder.

Choose Collection

Select which collection to save the request to.

Method 2: Add from Collection Menu

Right-Click Collection

Right-click on any collection in the sidebar.

Select "Add Request"

Choose "➕ Add Request" from the menu.

Name and Configure

Give the request a name and configure it.

Organizing with Folders

Create folders within collections for better organization:

Right-Click Collection

Right-click the collection where you want to add a folder.

Select "Add Folder"

Choose "📁 Add Folder" from the context menu.

Name Your Folder

Enter a folder name like "User Endpoints" or "Admin APIs".

Add Requests to Folder

Drag requests into the folder or save new requests directly to it.

Example Structure

📁 E-Commerce API
  ├── 📁 Authentication
  │   ├── POST Login
  │   ├── POST Register
  │   └── POST Logout
  ├── 📁 Products
  │   ├── GET All Products
  │   ├── GET Product by ID
  │   ├── POST Create Product
  │   └── DELETE Product
  └── 📁 Orders
      ├── GET User Orders
      ├── POST Create Order
      └── GET Order Status

Collection-Level Authentication

Set authentication once for all requests in a collection:

Right-Click Collection

Right-click the collection in the sidebar.

Select "Authorization"

Choose "🔐 Authorization" from the menu.

Configure Authentication

Choose auth type and enter credentials:

Bearer Token
Basic Auth
API Key
OAuth 2.0
And more...

All Requests Inherit

Every request in the collection automatically uses this authentication!

Override When Needed: Individual requests can override collection auth if necessary.

Collection Variables

Define variables shared across all requests in a collection:

Open Collection Variables

Right-click collection → "Variables"

Add Variables

Define key-value pairs:

baseUrl = https://api.example.com
apiVersion = v2
timeout = 5000

Use in Requests

Reference with double curly braces:

{{baseUrl}}/{{apiVersion}}/users

Variable Priority

Variables are resolved in this order:

Environment Variables (highest priority)
Collection Variables
Global Variables (lowest priority)

Managing Collections

Rename Collection

Right-click → "✏️ Rename" → Enter new name

Duplicate Collection

Right-click → "📋 Duplicate" → Creates exact copy

Delete Collection

Right-click → "🗑️ Delete" → Confirm deletion

Warning: Deleting a collection removes all its requests and folders!

Export Collection

Right-click → "📤 Export" → Save as JSON file

Collapse/Expand

Click the ▶ or ▼ icon to show/hide collection contents.

Best Practices

1. Use Descriptive Names

Name collections clearly: "User Management API" not "Collection 1"

2. Group Logically

Organize by feature, service, or workflow

3. Use Folders

Create folders for large collections

4. Set Collection Auth

Configure auth once at collection level

5. Use Variables

Leverage collection variables for shared values

6. Export Regularly

Back up important collections

Example Collection Structures

Microservices API

📁 Microservices Platform
  ├── 📁 User Service
  │   ├── GET Users
  │   └── POST Create User
  ├── 📁 Product Service
  │   ├── GET Products
  │   └── POST Create Product
  └── 📁 Order Service
      ├── GET Orders
      └── POST Create Order

Testing Collection

📁 API Test Suite
  ├── 📁 Smoke Tests
  │   ├── Health Check
  │   └── Version Check
  ├── 📁 Integration Tests
  │   ├── User Flow
  │   └── Payment Flow
  └── 📁 Load Tests
      └── High Volume Orders