Product documentationUpdated October 6, 2025
Project
Projects are the workspace for your specs, endpoints, tests, and runs in Total Shift Left—create one to start building coverage and CI-ready quality gates.
Overview
A project is the workspace where you organize an API from spec → endpoints → tests → runs. It’s the starting point for:
- importing or syncing an OpenAPI/Swagger spec
- grouping endpoints into features
- creating test cases and test run packs
- managing environments and access controls
If you’re new, start with Getting started and Initial configuration.
Create a project
- Go to Projects.
- Select New project.
- Fill in:
- Name (clear and specific, e.g. “User Management API”)
- Description (optional, but helpful for teams)
- Default environment (start with Dev/QA until runs are stable)
- Select Create.
Recommended conventions
- Name projects by domain: align with an API boundary (Billing, Identity, Orders).
- Keep environments separate: dev vs stage vs prod—avoid mixing credentials and data.
- Set access early: assign roles so editing, running, and viewing permissions are clear.
What to do next
- Add endpoints: Endpoint import and discovery
- Organize them: Feature management
- Configure variables: Test configuration
- Run a first validation: Test run
Related articles
Related articles
- Managing Projects · Product documentation
- Project Operations · Product documentation
- Project Settings · Product documentation
Next steps
- Getting started · Install + connect your spec
- Configuration fundamentals · Stabilize runs
- Initial configuration · Users, licensing, projects
- Release notes · Updates and fixes
Still stuck?
Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.