Provider:MaterializeAsyncAPI: v2.6.0Spec: Materialize Streaming Sources and SinksOperations: 1Messages: 5
Channel address
kafka/source/{topic}
Parameters
topic — Kafka topic name supplied via the TOPIC option of CREATE SOURCE.
Operations
subscribe
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.