diff --git a/pages/edge-services/how-to/create-pipeline-lb.mdx b/pages/edge-services/how-to/create-pipeline-lb.mdx
index 9e1adaa25b..6a7e475b27 100644
--- a/pages/edge-services/how-to/create-pipeline-lb.mdx
+++ b/pages/edge-services/how-to/create-pipeline-lb.mdx
@@ -71,6 +71,16 @@ If you see the message `Edge Services was unable to contact the host via the Loa
 - **Origin host**: Ensure that you entered the correct origin host, with no typos, for a host that exists behind the selected Load Balancer.
 - **Load Balancer ACLs**: Ensure that there are no [ACLs](/load-balancer/how-to/create-manage-acls/) configured on your Load Balancer which are blocking traffic from Edge Services.
 
+## WebSocket support
+
+If you want Edge Services to be able to forward WebSocket requests to the Load Balancer, you must enable a specific parameter via the Edge Services API.
+
+Make a call to the [Update backend stage](https://www.scaleway.com/en/developers/api/edge-services/#path-backend-stages-update-backend-stage) endpoint, to enable the `has_websocket` parameter in the `scalway_lb` object.
+
+If you do not enable `has_websocket`, WebSocket requests will not be forwarded to the Load Balancer. This means that any client attempting to establish a WebSocket connection to the Load Balancer origin via Edge Services will experience a failed connection or a 400/500 HTTP error.
+
+This parameter cannot yet be set via the Scaleway console.
+
 ## Help for Kubernetes Load Balancers
 
 If you are setting up an Edge Services pipeline for a [Kubernetes Kapsule](/kubernetes) Load Balancer, follow these steps to determine which Load Balancer and frontend to configure for your pipeline: