From 0164b7cc4e60451665fafc2e8ccdb7855237ed29 Mon Sep 17 00:00:00 2001
From: Jake Ginnivan <jake@ginnivan.net>
Date: Tue, 26 Sep 2017 22:04:09 +0800
Subject: [PATCH] Added info on how to find the browserWSEndpoint (#780)

---
 docs/api.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/api.md b/docs/api.md
index a36b41474240d..87d6f8b0d755e 100644
--- a/docs/api.md
+++ b/docs/api.md
@@ -228,7 +228,9 @@ Closes browser with all the pages (if any were opened). The browser object itsel
 - returns: <[string]> Browser websocket url.
 
 Browser websocket endpoint which could be used as an argument to
-[puppeteer.connect](#puppeteerconnectoptions).
+[puppeteer.connect](#puppeteerconnectoptions). The format is `ws://${host}:${port}/browser/<id>`
+
+You can find the `webSocketDebuggerUrl` from `http://${host}:${port}/json/version`. Learn more about the [devtools protocol](https://chromedevtools.github.io/devtools-protocol) and the [browser endpoint](https://chromedevtools.github.io/devtools-protocol/#how-do-i-access-the-browser-target).
 
 ### class: Page