List events

GET /v1/auto/events

Auto → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/auto/events`
Method	`GET`
Operation	`get_auto_events`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Holds one text/event-stream open and writes a frame each time one of your jobs or automations changes: event: job with the job as GET /v1/auto/jobs/{id} answers it, and event: automation with the automation as GET /v1/auto/automations/{id} answers it. Only your own rows are sent; another member's never are. Authenticate with Authorization: Bearer — a fetch-based reader, since a browser EventSource cannot set it. A : ping comment is written every 15 seconds, and the server closes the stream after 15 minutes; reconnect and re-read the lists. Frames carry no id: the lists are the truth, and the stream is a live hint over them.

Request

GET /v1/auto/events takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`2XX`	string	Success

2XX body — 1 field.

Field	In	Type	Always	Description
`(body)`	body	string (binary)	yes

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo auto events

.ts

.py

.go

.rs

.java

import { Configuration, AutoApi } from 'hanzoai';

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

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AutoApi(client).get_auto_events()

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

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

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

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

let result = auto_api::get_auto_events(&cfg, Default::default()).await?;

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

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

var result = new AutoApi(client).getAutoEvents();

curl https://api.hanzo.ai/v1/auto/events \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches auto through the auto tool, which names its 26 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": "list_auto_automations"
         }
       }
     }'

Auto API · All Hanzo APIs · Interactive reference

Was this page useful?

Broken link or missing step? Drop it in #docs on Discord or open a PR.

PreviousList automations NextList versions