List health — GET /v1/event/insights/health

Reports that the unified insights surface is serving.

GET /v1/event/insights/health

Event → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/event/insights/health`
Method	`GET`
Operation	`get_event_insights_health`
Auth	`Authorization: Bearer $HANZO_API_KEY`

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/event/health.

Request

GET /v1/event/insights/health takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	event.insightsStatus	ok
`default`	problem-details	refused

200 body — 3 fields.

Field	In	Type	Always	Description
`engine`	body	string	—	Engine names the engine serving the surface: hanzo-analytics.
`ok`	body	boolean	—	OK is always true — reaching this route is the liveness fact it reports.
`surface`	body	string	—	Surface is the path prefix this status covers: /v1/event/insights.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo event insights health

.ts

.py

.go

.rs

.java

import { Configuration, EventApi } from 'hanzoai';

const api = new EventApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getEventInsightsHealth();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import EventApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = EventApi(client).get_event_insights_health()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.EventAPI.GetEventInsightsHealth(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, event_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = event_api::get_event_insights_health(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.EventApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new EventApi(client).getEventInsightsHealth();

curl https://api.hanzo.ai/v1/event/insights/health \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches event through the event tool, which names its 9 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_event_economic"
         }
       }
     }'

Event API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList events NextList overview