diff --git a/documentation/modules/con-requests-kafka-bridge.adoc b/documentation/modules/con-requests-kafka-bridge.adoc
index 40b60557..8e241113 100644
--- a/documentation/modules/con-requests-kafka-bridge.adoc
+++ b/documentation/modules/con-requests-kafka-bridge.adoc
@@ -19,7 +19,7 @@ API request and response bodies are always encoded as JSON.
 Content-Type: application/vnd.kafka.v2+json
 ----
 
-* When performing producer operations, `POST` requests must provide `Content-Type` headers specifying the _embedded data format_ of the messages produced. This can be either `json` or `binary`.
+* When performing producer operations, `POST` requests must provide `Content-Type` headers specifying the _embedded data format_ of the messages produced. This can be either `json`, `binary` or `text`.
 +
 [cols="35,65",options="header",stripes="none",separator=¦]
 |===
@@ -33,6 +33,9 @@ m¦Content-Type: application/vnd.kafka.json.v2+json
 ¦Binary
 m¦Content-Type: application/vnd.kafka.binary.v2+json
 
+¦Text
+m¦Content-Type: application/vnd.kafka.text.v2+json
+
 |===
 
 The embedded data format is set per consumer, as described in the next section.
@@ -42,9 +45,9 @@ An empty body can be used to create a consumer with the default values.
 
 == Embedded data format
 
-The embedded data format is the format of the Kafka messages that are transmitted, over HTTP, from a producer to a consumer using the Kafka Bridge. Two embedded data formats are supported: JSON and binary.
+The embedded data format is the format of the Kafka messages that are transmitted, over HTTP, from a producer to a consumer using the Kafka Bridge. Three embedded data formats are supported: JSON, binary and text.
 
-When creating a consumer using the `/consumers/_groupid_` endpoint, the `POST` request body must specify an embedded data format of either JSON or binary. This is specified in the `format` field, for example:
+When creating a consumer using the `/consumers/_groupid_` endpoint, the `POST` request body must specify an embedded data format of either JSON, binary or text. This is specified in the `format` field, for example:
 
 [source,json,subs="attributes+"]
 ----