Authentication

Authentication lives under /api/v1/auth/. Every endpoint outside /auth/register and /auth/login requires Authorization: Bearer <api-key>. The route file is app/api/routes/auth.py.

`POST /auth/register`

Create a new user account and receive an API key. Request body (RegisterRequest):

{
  "email":    "demo@example.com",
  "name":     "Demo User",
  "password": "..."
}

Response (201 Created, RegisterResponse):

{
  "id":       "...",
  "email":    "demo@example.com",
  "api_key":  "ck-..."
}

The api_key is shown once. Store it securely. Exchange credentials for an API key. Request body (LoginRequest):

{ "email": "demo@example.com", "password": "..." }

Response (LoginResponse): same shape as register.

`POST /auth/rotate`

Rotate the calling user’s API key. Old key is invalidated; new one is returned.

POST /api/v1/auth/rotate
Authorization: Bearer <current-api-key>

Response (RotateKeyResponse):

{ "api_key": "ck-new..." }

`GET /auth/me`

Return the current user.

GET /api/v1/auth/me
Authorization: Bearer <api-key>

Response (UserResponse):

{
  "id":    "...",
  "email": "demo@example.com",
  "name":  "Demo User",
  "role":  "VIEWER"
}

Roles

The codebase recognises ADMIN, OPERATOR, APPROVER, AUDITOR, VIEWER, and POLICY_AUTHOR. Endpoints that require a specific role declare it via the require_role(...) dependency - see the per-endpoint docs.

Get started

Concepts

Guides

Integrations

API

Reference

`POST /auth/register`

`POST /auth/rotate`

`GET /auth/me`

Roles

See also

​POST /auth/register

​POST /auth/login

​POST /auth/rotate

​GET /auth/me

​Roles

​See also

`POST /auth/register`

`POST /auth/login`

`POST /auth/rotate`

`GET /auth/me`

Roles

See also