> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/developing-with-ndi/utilities/bridge-service-for-windows/webhooks.md).

# Webhooks

NDI Bridge Service supports change subscriptions which allow you to observe changes to any value instead of polling. To register a webhook, append the following path to the target API value where the `callback` query parameter is set to the URL you wish to receive POST requests from:

`/subscribe?callback=https://myurl`

For instance, if you wanted to subscribe to changes on the host port value you would do:

`api/host/port/subscribe?callback=https://myurl`

If a subscription is successful, you will revive a GUID as a response. This GUID is the handle for your subscription. If you want to unsubscribe from any change subscription you call the following URL (do not appended to the target API path) with the `id` query parameter being set to the GUID you received from the subscribe response:

`http://localhost:8080/api/unsubscribe?id=`

Change subscriptions are POSTed to the callback URL as JSON with *key* being the target API path (like `host/port` ) and *value* being the current value or ”Value changed.” for security sensitive values.

Active webhooks can be seen under the **Webhooks** section of the web interface.

![Command Line Interface](https://content.gitbook.com/content/DO9LSaUxLOBIgPjyrjR1/blobs/ml8M2fJciMsqyBoZbuja/14.jpeg)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ndi.video/all/developing-with-ndi/utilities/bridge-service-for-windows/webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.