Errors returns the caller org's most recently captured errors, newest first.
Errors returns the caller org's most recently captured errors, newest first.
GET /v1/event/errors
| Address | https://api.hanzo.ai/v1/event/errors |
| Method | GET |
| Operation | get_event_errors |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Errors returns the caller org's most recently captured errors, newest first. The error-tracking read view over event.error — the plane table the write core's error facts land in (errors are DELIBERATELY not on event.event) — each with its captured exception surfaced from the attributes map as a first-class field.
The org is the validated principal's — never a parameter — and this read requires a real bearer, NEVER the write-only publishable key: pk- can attribute a write and can read nothing. 403 without a validated bearer, 503 when the warehouse is unreachable.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
limit | query | integer | — | Limit is how many rows to return, newest first. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | errorList | ok |
200 body — 13 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | capturedError[] | — | Data is the errors, newest first. |
data[].distinctId | body | string | — | DistinctID is the person/visitor the error is attributed to. |
data[].event | body | string | — | Event is the event name the error was stored under, e.g. |
data[].exception | body | any | — | Exception is the captured error itself — the {type, message, stack, handled} object, already redacted at the fold point. |
data[].id | body | string | — | ID is the row's stable event id — the client's own idempotency id when it sent one, else the server-minted one. |
data[].library | body | string | — | Library is the client SDK that reported the error. |
data[].libraryVersion | body | string | — | LibraryVer is that SDK's version. |
data[].path | body | string | — | Path is the URL's path component. |
data[].product | body | string | — | Product is the surface that emitted the error. |
data[].properties | body | any | — | Properties is the row's whole property bag, returned verbatim as stored — any JSON object, $exception included. |
data[].sessionId | body | string | — | SessionID groups the events of one visit. |
data[].timestamp | body | string | — | Timestamp is when the error was captured, RFC3339 UTC. |
data[].url | body | string | — | URL is the full page address the error fired on. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, EventApi } from 'hanzoai';
const api = new EventApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getEventErrors();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_errors()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.EventAPI.GetEventErrors(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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_errors(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.EventApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new EventApi(client).getEventErrors();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/event/errors \
-H "Authorization: Bearer $HANZO_API_KEY"The door declares no tool for event — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?