Skip to main content

Organizing Requests

A good pattern is one collection per API or project, with folders for logical groups:

📁 My API (collection)
├── 📁 Auth
│   ├── POST /login
│   ├── POST /logout
│   └── POST /refresh-token
├── 📁 Users
│   ├── GET /users
│   ├── GET /users/:id
│   ├── POST /users
│   └── DELETE /users/:id
└── 📁 Products
    ├── GET /products
    └── POST /products

Using Variables for Base URL​

Instead of repeating the full URL in every request, store the base URL in a collection variable or environment variable:

  1. Open the Collection Overview tab
  2. Add a collection variable: baseUrl = https://api.myapp.com
  3. In each request URL, use {{baseUrl}}/users

When you switch to a staging environment with baseUrl = https://staging.myapp.com, all requests update automatically.

Request Naming Conventions​

Use clear, consistent names:

ConventionExample
METHOD /pathGET /users, POST /auth/login
Descriptive actionList all users, Create order

Auto-Save​

Rostyman automatically saves your open tabs every 30 seconds (configurable in Settings). The session is also restored on next launch — your unsaved tabs, scroll position, and active tab are all remembered.

Tab Indicators​

  • Orange ● — unsaved changes (request modified but not saved to collection)
  • Green ● — tab has meaningful content (params, headers, body, auth, or scripts)