Hanzo
OpenapiMetrics

Append samples to your org's named, labelled series

Takes `{series:[{name, labels, samples:[{t, v}]}]}`, appends every sample, creating each series on first write, and answers `{written}` — again counting…

POST /v1/metrics/write

Addresshttps://api.hanzo.ai/v1/metrics/write
MethodPOST
Operationpost_metrics_write
AuthAuthorization: Bearer $HANZO_API_KEY

Takes {series:[{name, labels, samples:[{t, v}]}]}, appends every sample, creating each series on first write, and answers {written} — again counting SAMPLES, so three series of ten samples is 30.

A series is identified by its name PLUS its whole label set, so adding one label makes a different series rather than annotating an existing one. Timestamps t are NANOSECONDS since the Unix epoch; a sample sent without one is stored at 0 and is then excluded by any query that sets a lower bound, which is the usual reason a write that reported success does not read back. Retention is per series and bounded — past 65536 samples the oldest are evicted.

The tenant is the gateway-minted X-Org-Id header, falling back to the deployment brand and then default. A body that does not decode is 400; nothing else is validated or rejected.

Request

The document declares no body for POST /v1/metrics/write. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_metrics_write, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo metrics write

Metrics API · All Hanzo APIs · Interactive reference

How is this guide?

On this page