diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md
index 338324afa82..c55dbb4fe51 100644
--- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md
+++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md
@@ -78,6 +78,7 @@ The above example uses secrets as plain strings. It is recommended to use a [sec
 | Field              | Required | Details | Example |
 |--------------------|:--------:|---------|---------|
 | host               | Y  | Address of the Pulsar broker. Default is `"localhost:6650"` | `"localhost:6650"` OR `"http://pulsar-pj54qwwdpz4b-pulsar.ap-sg.public.pulsar.com:8080"`|
+| listenerName       | N  | Selects which of a broker's [advertised listeners](https://pulsar.apache.org/docs/3.0.x/concepts-multiple-advertised-listeners/) the client connects through, for brokers that expose more than one network endpoint (for example separate internal and external addresses). The value is a single listener **name** that must match one the broker operator defined in its `advertisedListeners` configuration — it is *not* the `<name>:pulsar://<host>:<port>` address map, which is configured on the broker, not in Dapr. Listener names are chosen by the operator; `internal` and `external` are common conventions rather than a fixed set of values. Default: `""` (no listener name is sent and the broker's default listener is used, so behavior is unchanged). | `"external"` |
 | enableTLS          | N  | Enable TLS.  Default: `"false"` | `"true"`, `"false"` |
 | tenant             | N  | The topic tenant within the instance. Tenants are essential to multi-tenancy in Pulsar, and spread across clusters.  Default: `"public"` | `"public"` |
 | consumerID         | N  | Used to set the subscription name or consumer ID.  | Can be set to string value (such as `"channel1"` in the example above) or string format value (such as `"{podName}"`, etc.). [See all of template tags you can use in your component metadata.]({{% ref "component-schema.md#templated-metadata-values" %}})