Create write — POST /v1/metrics/logs/write

Takes {records:[{t, level, body, labels}]}, appends each one, and answers {written}.

POST /v1/metrics/logs/write

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

Takes {records:[{t, level, body, labels}]}, appends each one, and answers {written}. Bodies are stored verbatim; labels are the indexed dimensions a query filters on, so what you do not label you can only find by substring.

t is NANOSECONDS since the Unix epoch. A record sent without one is stored at 0 and then falls outside any query carrying a lower bound — the usual reason a successful write does not read back. Retention is a bounded ring, 1048576 records per org, oldest evicted first. No record is validated or rejected, so written is the number of records SENT; only a body that does not decode at all is 400.

The tenant is the gateway-minted X-Org-Id header, falling back to the deployment brand and then default; each org's records live in its own WAL-durable store.

Request

The document declares no body for POST /v1/metrics/logs/write. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for post_metrics_logs_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 logs write
import { Configuration, MetricsApi } from 'hanzoai';

const api = new MetricsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postMetricsLogsWrite();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import MetricsApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MetricsApi(client).post_metrics_logs_write()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.MetricsAPI.PostMetricsLogsWrite(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, metrics_api};

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

let result = metrics_api::post_metrics_logs_write(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MetricsApi;

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

var result = new MetricsApi(client).postMetricsLogsWrite();
curl -X POST https://api.hanzo.ai/v1/metrics/logs/write \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP declares no tool for metrics — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.


Metrics API · All Hanzo APIs · Interactive reference

Was this page useful?