Projects

Projects are the top-level containers in Routebase. Each project groups everything that belongs to one API effort — API specifications, environments, variables, test suites, mock servers, documentation, and monitors — and gives your team one place to work on it.

The Projects page

Open Projects from the main navigation. The page uses a three-column layout:

Column	What it shows
Projects (left)	All projects in your organization. Expand a project to see its environments and their variable counts.
Overview (middle)	The dashboard for the selected project, with inline-editable name and description.
API Specifications (right)	The specs in the selected project. Click a spec to open it in the API Designer; right-click to rename or delete it.

The columns are resizable, and the right panel can be collapsed. If no project is selected, the middle panel shows a Select a project empty state with a New Project button.

Creating a project

1. On the Projects page, click the + button (Add project) at the top of the project list — or Create project in the empty state.
2. Enter a Name (2–100 characters). Routebase shows a preview of the URL slug generated from the name.
3. Optionally add a Description.
4. Optionally expand Advanced options:
   • Environments — choose which environments to create. Defaults: Development, Staging, Production. You can also add Test and Custom (with your own name). See Environments.
   • Mock Server — create a mock server for frontend development right away.
   • Sample Test Data — seed the project with ready-to-use fixtures and seeds: None, Hello World Starter (3 fixtures plus a /health ping seed), or Pet Store (rich demo) (5 fixtures plus 2 seeds). See Test Data.
5. Click Create. You land directly in the new project.

The project overview

The middle panel shows a live dashboard for the selected project:

• Stat cards — Endpoints (with draft count), Schemas (with unused count), Test Pass Rate, and Mock Rules. Each card links to the matching feature.
• Environments — the project's environments at a glance.
• Recent Test Runs — the latest runs with a View all shortcut to the test runner.
• API Coverage — bars for documentation, test, and mock coverage.
• Version History — recent spec versions.
• Quick Actions — shortcuts like New Spec, Run Tests, and Mock Server.

Renaming and editing a project

Two ways to edit:

• Inline — click the project name or description in the overview header (the tooltip says Click to modify), type, and press Enter.
• Edit dialog — right-click the project in the list and choose Edit to change the name and description in a dialog.

Deleting a project

Deleting a project permanently removes all of its data — API specifications, environments, variables, test suites, and mock server rules. There is no undo.

1. Right-click the project in the list and choose Delete, or open Project Settings and use the Danger Zone → Delete Project.
2. Confirm in the Delete Project dialog.

Deleting requires the projects:delete permission (Admins and Owners); the option is hidden for Members.

Project settings

With a project selected, click Project Settings at the bottom of the project list. The settings sheet contains:

Section	Settings
General	Default Environment (used when no specific environment is selected), Request Timeout (1–300 seconds), Default Response Format (JSON or XML).
Features	Toggles for Mock Server, API Testing, and Auto Documentation in this project.
Authentication by Environment	Overview of the auth configuration per environment — see Project Auth.
Webhooks	Receive notifications when test runs complete — see Webhooks.
API Style Guide	Override style guide rule severities for this project — see Style Guide.
Header Policies	Project-level header policies; organization-wide policies are inherited and read-only — see Header Policies.
Danger Zone	Delete the project.

Changes are saved with the Save Changes button that appears once you edit a setting.

Switching projects

The project switcher sits in the header whenever you work inside a project. Click the project name (or press Ctrl+P / Cmd+P) to open it:

• Search projects by name or slug.
• Favorites — star a project to pin it to the top.
• Recently used — your last five projects.
• All Projects — everything else.
• New Project — jump straight to project creation.

Switching keeps you on the current page where it makes sense — for example, switching projects while in the API Designer, test runner, or mock server stays in that tool with the new project's data.

Members and access

Project access is governed by your organization's roles and, optionally, team assignments:

• Members can view projects (projects:read) and work on specs and tests, but cannot create, edit, or delete projects.
• Admins and Owners can create and edit projects (projects:write) and delete them (projects:delete).
• With Team Access (Starter and above), teams can be assigned to specific projects with a Read or Write role, restricting what non-admin members can touch. See Team Access.

Plan limits

Project and spec counts are gated by your plan:

Plan	Projects	Specs per project
Free	2	3
Starter	10	10
Pro / Enterprise	Unlimited	Unlimited

When you approach a limit, an upgrade nudge appears above the project list; at the limit, creating opens an upgrade dialog. Projects that exceed your plan's limit (for example after a trial ends) become read-only and are marked with a lock icon — upgrade to edit them again. See Billing.

Related

• Environments — development, staging, production and more per project
• Variables — configuration values across org, project, and personal scopes
• Project Auth — authentication configuration per environment
• Team Access — restrict projects to specific teams
• Billing — plans and limits