Projects & API Keys
Accurate project boundaries, scoped keys, and API registration flow in Nolax.
Projects keep ownership, access and reporting separate as your API estate grows.
What is a project
A project is the unit of SDK instrumentation. Each project has its own API key, and the SDK tags every request from an app instance with that project.
You can have several projects in one company account. Use one per application, for example your main API, a background worker API and a partner API.
Creating a project
Go to Projects → New Project and provide:
- Project name (required)
- Description (optional)
Split projects along operational boundaries such as customer-facing APIs, internal APIs, regional stacks or business units. Incident response and audit reports are easier when each project has one owner.
API key format
nlx_proj_xxxxxxxxxxxxxxxxxxxx
A key works for one project and only for SDK ingestion (POST /ingest with the
X-Nolax-Key header). It does not authenticate dashboard API requests.
Automatic API detection
Once the SDK is running with a project key, Nolax groups live traffic by API path and environment as requests arrive. A new project shows data without any manual setup.
Register an API explicitly when you want to control how it is named and owned in reports and alerts.
Finding your keys
You can see keys in:
- Settings → API Keys (across projects)
- Project detail → SDK Key (single project context)
Store API keys in environment variables. Never commit them to source control.
Handling keys
- Store keys in a secret manager
- Inject keys at runtime through environment variables
- Limit visibility to trusted operators
- Rotate keys on a regular cadence and immediately on exposure
Rotating a key
Go to Projects → [your project] → Rotate key.
Type ROTATE to confirm. After rotation:
- The old key stops working immediately
- Any running SDK instance with the old key fails to ingest
- The new key is shown once in full, so copy it before you close the dialog
In production, prepare the new secret and the deployment before you rotate.
Steps:
- Update runtime secrets with the new key
- Roll deployments across all services
- Validate ingestion and request auth
- Complete rotation confirmation in Nolax
API registration flow
Inside a project, click Add API and provide:
- HTTP method (
GET,POST,PUT,PATCH,DELETE) - API path (must start with
/) - Environment (
production,staging,development)
A registered API shows request volume, error rate, latency (including p95), and active alerts by API.
Environments
The SDK takes an environment setting that separates production, staging and
development traffic within one project. The accepted values are production,
staging and development.
The dashboard shows each environment separately, and alert rules can be scoped to one.
Next steps
- 1Alerts
Create threshold rules for the APIs inside this project.
- 2Compliance Reports
Use project-scoped data as evidence for audit-ready reporting.

