ClickHouse Kafka Table Engine (Consumer-Side Streaming)
Version 1.0.0
AsyncAPI description of the documented streaming surface that ClickHouse offers through the Kafka table engine. ClickHouse itself does NOT publish a public WebSocket, Server-Sent Events, or push-style streaming endpoint. Instead, ClickHouse (self-managed and ClickHouse Cloud) acts as a Kafka *consumer*: a CREATE TABLE statement using the Kafka() engine subscribes the ClickHouse server to one or more topics on an externally hosted Kafka-compatible broker (Apache Kafka, Confluent Cloud, Redpanda, AWS MSK, Azure Event Hubs, WarpStream). Messages pulled from those topics are then typically routed into a MergeTree table via a MATERIALIZED VIEW. This AsyncAPI document models that consumer-side contract: the channel the operator declares, the Kafka engine parameters used to bind to it, the virtual columns exposed on the resulting ClickHouse table, and the supported message formats. The same consumer-side model applies to ClickPipes in ClickHouse Cloud, which is a managed wrapper around equivalent ingestion sources.
Channels
Messages
Servers
AsyncAPI Specification
Work with this as data
Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for asyncapi
4 MCP tools reach this
find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/asyncapis/clickhouse-kafka-engine-asyncapi"
curl "https://apis.io/api/v1/asyncapis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.