AsyncAPI channel · Materialize · Materialize Streaming Sources and Sinks

kafka/source/{topic}

Kafka topic consumed by a Materialize Kafka source. Syntax (abbreviated): CREATE SOURCE [IN CLUSTER ] FROM KAFKA CONNECTION ( TOPIC '' [, GROUP ID PREFIX ''] [, START OFFSET (, ...)] [, START TIMESTAMP ] ) FORMAT [ENVELOP

Open source AsyncAPI → All Materialize channels Materialize provider profile
Provider: Materialize AsyncAPI: v2.6.0 Spec: Materialize Streaming Sources and Sinks Operations: 1 Messages: 5

Channel address

kafka/source/{topic}

Parameters

Operations

receiveFromKafkaSource
Materialize ingests messages from the configured Kafka topic.

Messages

kafkaSourceAvroRecord
Avro-encoded record consumed by Materialize via Confluent Schema Registry.
Content-Type: application/vnd.apache.avro+binary
kafkaSourceJsonRecord
JSON-encoded record stored as a single jsonb column named data.
Content-Type: application/json
kafkaSourceProtobufRecord
Protobuf-encoded record decoded via schema registry or inline schema.
Content-Type: application/x-protobuf
kafkaSourceTextRecord
UTF-8 text with newline delimiters.
Content-Type: text/plain
kafkaSourceBytesRecord
Raw bytes with no decoding.
Content-Type: application/octet-stream

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.