Projects

Projects are the most powerful way to organize your API work in Tigrister. While Box lets you save individual requests, Projects provide a structured way to manage entire APIs with modules, endpoints, environments, and servers.

Structured Organization

Projects bring structure to your API work. Instead of a flat list of saved requests, you get a hierarchical tree of modules and endpoints that mirrors your API design.

When to Use Projects

Projects are ideal when:

📦Working with a Complete API

You're building, testing, or documenting an API with multiple related endpoints that share common base URLs and authentication.

🌍Multiple Environments

You need to test the same endpoints against different environments (development, staging, production) with different variables.

🏗️API Design

You're designing an API and want to define expected responses, validate contracts, and maintain documentation.

📋Logical Grouping

You want to organize endpoints into logical groups (modules) like "Users", "Products", "Orders", etc.

Projects vs Box vs History

Understanding when to use each feature:

FeatureProjectsBoxHistory
OrganizationHierarchical (modules)Flat listChronological
EnvironmentsPer-project environmentsUses globalSnapshot only
ServersMultiple base URLsIndividual URLsRecorded URL
Contract ValidationFull supportCustom schema onlyNo
Response SavedExpected responsesNoFull response
Best ForAPI developmentQuick savesRequest audit

Project Structure

Every project follows a clear hierarchy:

My API Project
Users(Module)
GETList Users
GETGet User by ID
POSTCreate User
PUTUpdate User
DELDelete User
Products(Module)
GETList Products
POSTCreate Product
Project
Top-level container
Module
Logical grouping
Endpoint
API request

Key Concepts

Modules

Modules are logical groups that organize related endpoints. Think of them as folders or categories. A "Users" module might contain all user-related endpoints like login, register, profile, etc.

Endpoints

Endpoints are the actual API requests within a module. Each endpoint has a method (GET, POST, etc.), a path, and can have its own headers, body, parameters, and expected responses.

Project Environments

Each project can have its own set of environments (Development, Staging, Production) with different variable values. When you switch environments, all endpoints automatically use the new values.

Servers

Servers define the base URLs for your API. A project can have multiple servers (e.g., https://api.example.com for production, https://staging.api.example.com for staging).

Quick Start

Get started with Projects in 4 steps:

1

Create a Project

Click "New Project" in the Projects section of the sidebar.

2

Add a Module

Use the project's menu (⋮) and select "Add Module".

3

Add Endpoints

Use the module's menu (⋮) and select "Add Endpoint".

4

Configure & Test

Click an endpoint to open it, configure the request, and send it.