26 System
3 operations.
26.0.1 getHealth
GET /api/health
Answers “is the application alive and are its dependencies reachable?” (no login — monitoring calls this before anyone signs in).
Why it exists. † Report whether the application, its database and the AI engine are each reachable, so a monitor or a deployment gate can tell a partial outage from a total one.
Unauthenticated container health check — reports API liveness plus Supabase and AI-server reachability. Returns 503 (never 500) when degraded.
Authentication: none
Returns — …health · details
Field names as the handler returns them; the source states no types for them.
Effect — reads profiles
Responses
| Status | Meaning | Body |
|---|---|---|
200 |
All checks healthy. | |
503 |
Degraded (same shape, status “degraded”) or unhealthy ({status, timestamp, error}). |
26.0.2 pushToIdms
POST /api/idms/push
Placeholder for pushing data to an IDMS system — accepts and acknowledges, nothing more yet.
Why it exists. ‡ Accept a payload pushed from the integrity data management system, for the integration that feeds findings in from outside the platform.
Called by — app/(authenticated)/w/integrity/actions/actions-client.tsx
Reached from — /w/integrity/actions
Stub IDMS ingest — authenticates the caller, accepts an arbitrary JSON payload, and acknowledges without persisting or forwarding. Cookie session only.
Authentication: CookieAuth
Returns — ok · receivedAt · userId · stub · bodyPreview
Field names as the handler returns them; the source states no types for them.
Responses
| Status | Meaning | Body |
|---|---|---|
200 |
Acknowledged (stub). | |
400 |
Invalid JSON. | Error |
401 |
Unauthorized. | Error |
26.0.3 logWorkspaceEvent
POST /api/workspaces/events
Records a workspace usage event in the server logs.
Why it exists. ‡ Accept a workspace activity event and write it to the structured server log, where the platform’s logging pipeline collects it.
Called by — lib/workspaces/context.tsx
Reached from — /datasets · /datasets/<slug> · /datasets/org/<id> · /organizations · /organizations/<id> · /w/data-explorer/anomalies …and 17 more
Telemetry sink — writes an authenticated workspace event to structured server logs. No persistence. Cookie session only.
Authentication: CookieAuth
Returns — ok
Field names as the handler returns them; the source states no types for them.
Responses
| Status | Meaning | Body |
|---|---|---|
200 |
Logged. | |
400 |
Invalid payload (not a JSON object). | Error |
401 |
Unauthorized. | Error |