Projects and API Registration

Projects group your APIs by owner. API registration tells Nolax which routes matter most.

Create your first project

Go to Projects → New Project and provide:

• Project name (required)
• Description (optional)

A project is the ownership boundary for APIs, metrics, alerts, insights, compliance reports, and API keys.

Splitting projects

Create a separate project for each ownership boundary, for example:

• Customer-facing APIs
• Internal APIs
• Regional stacks
• Distinct business units

Separate projects give you cleaner reports, faster triage and independent key rotation. If nobody can say who owns an API, the project is too broad.

Register APIs in the project

Inside a project, click Add API and provide:

• HTTP method (GET, POST, PUT, PATCH, DELETE)
• API path (must start with /)
• Environment (production, staging, development)

Once an API is registered, the project shows its:

• Request volume
• Error rate
• Latency, including p95
• Active alerts

Environments

Use the three labels consistently:

• production: traffic from real customers
• staging: release validation
• development: integration and local testing

Mixed labels put test traffic into production alerts and insights.