Insights
Insights — 2 operations on https://api.hanzo.ai.
The REST reference for Insights — 2 operations, generated from the OpenAPI document.
| Base URL | https://api.hanzo.ai |
| Operations | 2 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
insights
InsightsEvents returns the caller org's most recent product events, newest first.
GET /v1/insights/events
InsightsEvents returns the caller org's most recent product events, newest first. The console's raw-event view over the same table the capture doors write: one row per stored event, with the caller's own property bag returned verbatim.
The org is the validated principal's — never a parameter — and a read requires a real bearer, never the write-only publishable key. 403 without a validated bearer, 503 when the warehouse is unreachable.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
limit | query | integer | — | Limit is how many rows to return, newest first. |
InsightsHealth reports that the unified insights surface is serving.
GET /v1/insights/health
InsightsHealth reports that the unified insights surface is serving. It reads no tenant data and consults no dependency, so it answers 200 unconditionally and needs no principal — liveness must be probe-able. The warehouse-connectivity probe is a different question and lives at GET /v1/analytics/health.
How is this guide?