Update AdminAPI.md (#3936)

* Update AdminAPI.md

Signed-off-by: Jason Syrotuck <jasyrotuck@gmail.com>

* Update AdminAPI.md

Signed-off-by: Jason Syrotuck <jasyrotuck@gmail.com>

* Update docs/features/AdminAPI.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Jason Syrotuck <jasyrotuck@gmail.com>

* Update docs/features/AdminAPI.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Jason Syrotuck <jasyrotuck@gmail.com>

---------

Signed-off-by: Jason Syrotuck <jasyrotuck@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: jamshale <31809382+jamshale@users.noreply.github.com>

Author: 3 people

docs/features/AdminAPI.md

@@ -39,7 +39,12 @@ Webhooks received over WebSocket will contain the same data as webhooks posted o
 * `payload`: The payload of the webhook; this is the data usually received in the request body when webhooks are delivered over HTTP
 * `wallet_id`: If using multitenancy, this is the wallet ID of the subwallet that emitted the webhook. This value will be omitted if not using multitenancy.
 
-To open a WebSocket, connect to the `/ws` endpoint of the Admin API.
+To open a WebSocket, connect to the `/ws` endpoint of the Admin API. E.g. If the Admin Swagger can be found at `http://localhost:3001`, the webhook websocket is at `ws://localhost:3001/ws`. 
+
+Websocket connection will also require two additional headers: 
+* `Authorization`: a JWT token prepended with `Bearer `
+* `X-API-key`: the admin API key value set via the --admin-api-key configuration parameter.
+
 
 ### Pairwise Connection Record Updated (`/connections`)