Logz.io
Logz.io is a managed cloud observability platform built on the ELK Stack (Elasticsearch / Logstash / Kibana, plus OpenSearch and Grafana) that unifies log management, infrastructure monitoring, distributed tracing, and Cloud SIEM behind a consumption-based pricing model. The platform pairs an AI Agent layer for root-cause analysis with native OpenTelemetry, Prometheus, Grafana, and Perses compatibility, and exposes its entire control plane through a single OpenAPI 2.0-described public API covering search, alerting, sub-account management, security rules, parsing pipelines, archive / restore, and visualization-as-code via the Logz.io fork of Grafana and Perses.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Logz.io the way a machine reads it — 44 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Logz.io scores 77.1/100 (exemplar), with a separate agent-readiness read of 34/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Logz.io
Each block below is one kind of artifact we hold for Logz.io. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Logz.io Search Logs API
Query indexed logs against the Logz.io managed Elasticsearch / OpenSearch cluster using a request body that mirrors the upstream Elasticsearch Search API. Includes `/v1/search` ...
Logz.io Archive and Restore API
Configure long-term archive destinations (S3, ADLS, Google Cloud Storage), test connectivity, list and delete archive settings, then restore archived logs back into Logz.io for ...
Logz.io Drop Filters API
Create, list, activate, deactivate, and delete drop filters that discard matching events before they enter Logz.io's hot index. The primary tool for trimming ingest volume and m...
Logz.io Alerts API
Manage Logz.io alert rules — create, retrieve, update, enable, disable, and delete log-based and multi-account alerts via `/v2/alerts`, list currently triggered alerts via `/v1/...
Logz.io Notification Endpoints API
Manage downstream notification destinations attached to alerts. Supports Slack, PagerDuty, Microsoft Teams, BigPanda, OpsGenie, ServiceNow, VictorOps, custom HTTPS webhooks, and...
Logz.io Users API
List, create, update, suspend, and delete users in the main account and across all associated sub-accounts. Includes authentication groups (SSO group-to-role mappings), the `who...
Logz.io Tokens API
Manage the three Logz.io credential types — API tokens (account control plane), log-shipping tokens (ingest authentication for shippers like Filebeat, Fluentd, OpenTelemetry, an...
Logz.io Accounts API
Provision and resize time-based log sub-accounts and metrics accounts. Lets owners split daily ingest quotas across environments, teams, or customers and reshape retention witho...
Logz.io Metrics Prometheus API
Prometheus-compatible read path against the Logz.io Infrastructure Monitoring backend. Implements `query`, `query_range`, `series`, `labels`, and `label/{name}/values` exactly a...
Logz.io Grafana API
Pass-through API to the Logz.io fork of Grafana plus a subset of upstream Grafana endpoints. Covers dashboards (`/api/dashboards`), folders, alert rules and silences (`/api/v1/p...
Logz.io Perses API
Logz.io's Perses-compatible dashboard API (Perses is the CNCF observability dashboard project Logz.io helps maintain). Manages projects, dashboards, global datasources, and the ...
Logz.io Cloud SIEM API
Logz.io Cloud SIEM control plane — manage detection rules (correlation and threshold), retrieve raised security events, and administer the SIEM sub-account. Backs the detect → t...
Logz.io Log Shipping API
Provision the Logz.io managed pull-side log shippers. Connect AWS CloudTrail streams and S3 buckets (with IAM assume-role) directly from the API so customers can stand up log co...
Logz.io Parsing Pipelines API
Manage Sawmill log-type pipelines and external mapping uploads. Sawmill is Logz.io's open-source JSON transformation engine; this API lets customers attach declarative parsing p...
Logz.io Lookup Lists API
CRUD for reference data used to enrich and filter logs and alerts. Customers upload lookup lists of IPs, hostnames, user IDs, or business identifiers and reference them by name ...
Logz.io Insights API
Retrieve the cognitive-insights and anomaly findings surfaced by Logz.io's AI observability layer. Returns ranked operational insights — Exceptions, Slow Transactions, Critical ...
Logz.io Deployment Markers API
Post deployment events into Logz.io as markers so they overlay on dashboards and contextual searches. The mechanism release pipelines use to correlate spikes in error logs or la...
Logz.io OpenSearch Snapshots API
Drive the OpenSearch / Kibana saved-object snapshot lifecycle inside Logz.io — import and export visualizations, searches, and dashboard objects programmatically. The promotion-...
Logz.io Audit Trail API
Query the Logz.io account-level audit trail and list the event types it emits. Customers wire this into their own SIEM or governance pipelines for ISO 27001 / SOC 2-style activi...
Scroll within the panel for all 19 ·
Arazzo Workflows 13
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Logz.io Verify Token And Discover Accounts
Confirm which account a token belongs to, then list its associated accounts.
ARAZZOLogz.io Alert Create, Update, And List
Create an alert, refine its threshold, then list all alerts to confirm it.
ARAZZOLogz.io Alert Enable/Disable Lifecycle
Create an alert, disable it for a maintenance window, re-enable it, and verify.
ARAZZOLogz.io Custom Webhook Endpoint Then Alert
Create a custom webhook notification endpoint and an alert that routes to it.
ARAZZOLogz.io Grafana Dashboard In New Folder
Create a Grafana folder, save a dashboard into it, and read it back by uid.
ARAZZOLogz.io Notification Endpoint Cleanup
List notification endpoints, confirm one by id, and delete it.
ARAZZOLogz.io Notification Endpoint Then Alert
Create a Slack notification endpoint, then wire a new alert to notify it.
ARAZZOLogz.io Grafana Contact Point Setup
Create a Grafana contact point, confirm it by name, and list alert rules.
ARAZZOLogz.io Metrics Explore And Query
Discover label names, list matching series, then run an instant PromQL query.
ARAZZOLogz.io Search Then Scroll Logs
Run a log search, then open a scroll to page through the full result set.
ARAZZOLogz.io Provision a Sub Account
Create a time-based log sub account, read it back, and adjust its retention.
ARAZZOLogz.io Upsert an Alert
Find an alert by title and update it if it exists, otherwise create it.
ARAZZOScroll within the panel for all 13 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Logz.io GraphQL Schema
Conceptual GraphQL schema for the Logz.io cloud observability platform. Logz.io unifies log management, infrastructure metrics, distributed tracing, and Cloud SIEM behind a sing...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Logz Io Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Logz Io Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Logz Io Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Logz.io API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Logz.io Alert Rule
JSON SCHEMALogz.io Log Document
JSON SCHEMALogz.io Metric Sample
JSON SCHEMALogz.io Search Request
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Logz.io — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Design & Contract 14
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 14 ·
Build 24
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 24 ·
Access & Security 5
Authentication, authorization, and security posture
Learn 3
Tutorials, courses, talks, and written guidance
Operate 7
Status, limits, changes, and where to get help
Scroll within the panel for all 7 ·
Commercial 7
Pricing, plans, and the legal terms of use
Scroll within the panel for all 7 ·
Company 6
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/logz-io · machine-readable index on apis.io