adding desc for an additional HTTP header for authentication

Author: gmzakpinar

content/en/docs/appstore/use-content/platform-supported-content/services/event-broker.md

@@ -109,6 +109,21 @@ Every event must carry four mandatory CloudEvents core attributes, each prefixed
 * specversion as `ce_specversion`
 * type as `ce_type`
 
+{{% alert color="info" %}}
+For HTTP Bridges, an additional HTTP header is required for authentication.
+{{% /alert %}}
+
+* **Authorization**: The value must be set as a Bearer token using the Personal Access Token (PAT) generated during bridge configuration.  
+  Example: `Authorization: Bearer <your-personal-access-token>`
+
+This header must be included in all HTTP requests sent to the Mendix Event Broker via the HTTP Bridge.  
+For details on how to obtain your Bearer token, see [Using the HTTP Bridge](#using-the-http-bridge).
+
+> **Note:**  
+> You can include additional HTTP headers in your request, such as `ce_time: 2025-06-13T15:36:52.148542+02:00`.  
+> For example, passing `ce_time` will set the published time of the event.  
+> All other custom HTTP headers will be forwarded as Kafka headers by default.
+
 See [CloudEvents](https://github.com/cloudevents/spec/blob/v1.0.1/spec.md#required-attributes) for more information on required attributes.
 
 ### Creating a Bridge
@@ -254,7 +269,7 @@ On the confirmation screen you can do the following:
 
     {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_6_http.png" class="no-border" >}}
 
-#### Using the HTTP Bridge
+#### Using the HTTP Bridge {#using-the-http-bridge}
 
 To run the HTTP bridge from your client, include a Bearer token in the request header.