# DataHub

**Canonical:** https://apis.io/providers/datahub/  
**Website:** https://datahub.com  
**APIs profiled:** 11

DataHub is LinkedIn's generalized metadata search and discovery platform, providing a unified data catalog, lineage graph, governance tooling, and event-driven Actions Framework. It exposes GraphQL, OpenAPI, and Rest.li APIs along with Python and Java SDKs and a CLI for metadata ingestion.

## Kin Score — 48.6 / 100 (developing)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 48.6).

| Facet | Score |
|---|---|
| Discoverability | 64.8 |
| Contract Quality | 69.3 |
| Governance | 28.8 |
| Contract Governance | 28.8 |
| Operational Transparency | 47.4 |
| Developer Ergonomics | 52.4 |
| Commercial Clarity | 23.7 |
| Access Clarity | 23.7 |

## Agent readiness — 37.2 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | no |
| Error Semantics | verified |
| OpenAPI Examples | no |
| Rate Limit Signal | documented |
| Event Surface Described | derived |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Enterprise · Self-serve signup — onboarding: self-serve, pricing: enterprise, trial: no (confidence: high).

## APIs (11)

- **DataHub GraphQL API** — Primary API for querying and mutating metadata in DataHub. The GraphQL API serves as the main public API for the platform and can be used to fetch and update metadata programmat...
- **DataHub REST API** — The Rest.li API represents the underlying persistence layer and exposes the raw PDL models used in storage. It powers the GraphQL API under the hood and is used for system-speci...
- **DataHub Python SDK** — Python client for interacting with DataHub. The acryl-datahub package provides a CLI and SDK for DataHub, including REST and Kafka emitter APIs for pushing metadata programmatic...
- **DataHub Java SDK** — Java client for interacting with DataHub. The io.acryl datahub-client package offers REST emitter APIs that can be used to emit metadata from JVM-based systems. It supports all ...
- **DataHub CLI** — Command line tool for interacting with DataHub. The datahub CLI allows you to perform common operations including metadata ingestion, entity management, and system administratio...
- **DataHub Actions Framework** — Event-driven framework for responding to real-time changes in the DataHub metadata graph. The Actions Framework allows you to configure event sources, transformations, and actio...
- **DataHub Batch API** — Batch operations for fetching multiple entities and their aspects in a single request. Supports version-specific retrieval and conditional writes.
- **DataHub Entities API** — Read, write, and delete metadata entities in the DataHub metadata graph. The entities endpoints support upserting entity-aspect pairs, retrieving the latest aspects for a given ...
- **DataHub Platform API** — Write metadata events using the standard platform format. Provides an alternative ingestion path for emitting metadata change proposals to the DataHub metadata graph.
- **DataHub Relationships API** — Query the relationship graph to navigate connections between entities. Supports filtering by relationship type and traversal direction (incoming or outgoing) from a given entity...
- **DataHub Timeline API** — Query the versioned history of entity aspects over time. Useful for tracking schema changes, documentation updates, and other temporal metadata modifications for a given entity.

## Agentic access (1)

- **Datahub Agentic Access** — 7 operations · 4 acting

## Security (2)

- **Datahub Authentication** — http · 1 scheme
- **Datahub Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC

## Plans (1)

- **Datahub Plans Pricing**

## Tags

Data Catalog, Data Discovery, Data Governance, Data Lineage, Metadata

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/datahub/). Scores are computed from the provider's own public artifacts under a published rubric.