Projects
Projects
Create, list, update, and delete projects, plus per-project usage stats
A project groups everything that belongs together for one service, environment, or team — log sources, repos, channels, analyses, and watchdog rules. The endpoints below cover the project lifecycle and a stats endpoint for per-project usage.
For a conceptual walkthrough, see Projects.
Endpoints
| Method + path | Purpose |
|---|---|
GET /v1/config/projects | List projects in your tenant |
POST /v1/config/projects | Create a project |
PUT /v1/config/projects/{id} | Update a project |
DELETE /v1/config/projects/{id} | Delete a project |
GET /v1/config/projects/{slug}/stats | Per-project stats by slug |
Project shape
Every project carries the following fields:
| Field | Type | Notes |
|---|---|---|
id | UUID | The project id |
name | string | Display name |
slug | string | URL-safe identifier; lowercase alphanumeric with hyphens |
description | string | null | Optional long-form description |
isDefault | boolean | Every tenant has exactly one default project; it cannot be deleted |
llmContext | string | null | A short paragraph describing your stack and quirks — improves diagnosis quality |
createdAt | ISO 8601 | When the project was created |
updatedAt | ISO 8601 | When the project was last updated |
Configuring a project
Once a project exists, the surrounding configuration lives behind its own endpoints and guides:
- Metadata — name, slug, description
- AI analysis context — the
llmContextfield - Access list — which users can run analyses from chat triggers (see also
/api/access-list) - Severity thresholds — minimum severity for notification routing
See also
- Projects guide — concepts and dashboard walkthroughs
- Authentication — required permissions per endpoint
- Errors — error code reference
- Idempotency — retry-safe write requests