GET /v1/config/projects/{slug}/stats

Per-project rollups — analysis count, log sources, repos, channels, watchdog status, and 30-day trend

Returns rollup counts and a 30-day analysis trend for one project, looked up by slug. Useful for project overview dashboards and admin tooling.

Authentication

API key with config:read permission.

Endpoint

GET /v1/config/projects/{slug}/stats

Path parameters

Param	Type	Notes
`slug`	string (1–100 chars)	The project slug — lowercase alphanumeric with hyphens

Response

200 OK

{
  "success": true,
  "data": {
    "analysisCount": 47,
    "logSourceCount": 2,
    "repoCount": 1,
    "notificationChannelCount": 3,
    "supportDeskCount": 1,
    "watchdogEnabled": true,
    "dailyTrend": [
      { "date": "2026-03-27", "count": 1 },
      { "date": "2026-03-28", "count": 4 },
      { "date": "2026-04-25", "count": 2 }
    ]
  }
}

Field	Type	Notes
`analysisCount`	int	Analyses created in the last 30 days
`logSourceCount`	int	Configured log sources on this project
`repoCount`	int	Connected source-code repositories
`notificationChannelCount`	int	Notification channels scoped to this project
`supportDeskCount`	int	Support-desk bindings on the tenant
`watchdogEnabled`	boolean	Whether watchdog monitoring is currently enabled on this project
`dailyTrend`	array	One entry per day with at least one analysis in the last 30 days
`dailyTrend[].date`	string (`YYYY-MM-DD`)	Calendar date (UTC)
`dailyTrend[].count`	int	Analyses created that day

dailyTrend only includes days that have at least one analysis. Days with zero analyses are omitted.

Error responses

Status	`error.code`	When
400	`VALIDATION_ERROR`	`slug` failed validation
401	`UNAUTHORIZED`	Missing or invalid API key
403	`FORBIDDEN`	Key lacks `config:read`
404	`NOT_FOUND`	No project with that slug in your tenant

Example

curl https://api.sigsentry.com/v1/config/projects/checkout-api/stats \
  -H "Authorization: Bearer ss_secret_..."