Skip to main content

Organization Strategies

Choose an organization strategy that fits your workflow:

By Project

Separate workspace per project

By Client

One workspace per client

By Environment

Dev, staging, production workspaces

By Team

One workspace per team

By Project

Organize workspaces by project:
Best for:
  • Multiple independent projects
  • Different tech stacks
  • Separate teams per project

By Client

Organize by client or customer:
Best for:
  • Consulting/agency work
  • Multiple clients
  • Client-specific configurations

By Environment

Separate workspaces by environment:
Best for:
  • Testing environment-specific configurations
  • Preventing accidental production changes
  • Clear environment separation

Collection Organization

Folder Structure

Organize requests into logical folders:

Naming Conventions

Use consistent naming: Collections:
  • User Management API
  • Payment Processing API
  • Notification Service API
Requests:
  • GET /users - List Users
  • POST /users - Create User
  • PUT /users/:id - Update User

Environment Management

Environment Strategy

One file per environment:

Best Practices

Clear, descriptive names for everything:
  • Workspaces
  • Collections
  • Requests
  • Environments
Don’t over-organize:
  • Start simple
  • Add structure as needed
  • Avoid deep nesting
Add README.md to workspaces:

Next Steps

Creating Workspaces

Create and configure workspaces

Git Collaboration

Team collaboration strategies

Local-First Workflow

Local-first best practices

Collections

Manage API collections