Zipkin
Zipkin is an open source distributed tracing system for gathering timing data to troubleshoot latency problems in microservice architectures. It was originally developed at Twitter based on the Google Dapper paper, and is now a CNCF-related project maintained by the OpenZipkin community. Zipkin provides a collector, storage, and query service with a UI for visualizing trace data across distributed services.
Zipkin publishes 6 APIs on the APIs.io network, including Autocomplete API, Dependencies API, Health API, and 3 more. Tagged areas include Distributed Tracing, Observability, Open Source, and Microservices.
The Zipkin catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.
Zipkin’s developer surface includes documentation and 11 more developer resources.
Kin Score
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Zipkin Autocomplete API
Autocomplete tag key and value lookups
Zipkin Dependencies API
Query service dependency links
Zipkin Health API
Server health check
Zipkin Services API
Query registered service names
Zipkin Spans API
Submit and query span names
Zipkin Traces API
Search and retrieve distributed traces
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Zipkin API v2
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Zipkin Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Zipkin Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Zipkin Finops
FINOPSFeatures 6
Notable capabilities this provider offers.
Distributed Tracing
End-to-end tracing of requests across microservices.
Span Collection
Ingestion of spans via HTTP, Kafka, and other transports.
Trace Search
Query traces by service, span name, tags, and time range.
Dependency Graph
Derived service-to-service dependency links from spans.
UI
Web-based UI for exploring traces and dependency graphs.
Pluggable Storage
Pluggable backends including in-memory, MySQL, Cassandra, and Elasticsearch.
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Zipkin Context
JSON-LDSpectral Rules 2
Spectral governance rulesets for linting and validating these APIs.
Zipkin API Rules
SPECTRALZipkin API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 4
JSON Structure definitions describing this provider's data shapes.
Zipkin Api V2 Annotation Structure
JSON STRUCTUREZipkin Api V2 Dependency Link Structure
JSON STRUCTUREZipkin Api V2 Endpoint Structure
JSON STRUCTUREZipkin Api V2 Span Structure
JSON STRUCTUREExamples 4
Example request and response payloads for these APIs.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers build with this provider.
Microservices Latency Debugging
Identify slow services and operations in a microservice architecture.
Error Investigation
Trace failed requests across services to find error origin.
Service Dependency Mapping
Visualize which services call which, with call counts.
Performance Optimization
Identify hotspots and optimize critical-path operations.
Integrations 5
Pre-built integrations with other platforms and tools.
Brave
Java instrumentation library for OpenZipkin.
OpenTelemetry
OpenTelemetry can export traces to Zipkin.
Spring Cloud Sleuth
Spring framework integration emitting Zipkin traces.
Kafka
Span transport via Kafka for asynchronous ingestion.
Elasticsearch
Storage backend for spans and traces at scale.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API