# How does notification-controller build the webhook URL path for a Receiver?

Flux CD, Hard (Expert), Security. https://k8wiz.com/uquiz/how-does-notification-controller-build-the-webhook-url-path-for-a-receiver

- A. /hook/ followed by a hash of the token, Receiver name and namespace
- B. /hook/<namespace>/<receiver-name>, with the token sent as a query string
- C. /webhook/<receiver-name> on port 9292 of the controller
- D. A random path generated once when the Receiver is created

**Answer:** /hook/ followed by a hash of the token, Receiver name and namespace

**Explanation:** The path is /hook/ plus a SHA-256 digest of the token from the Receiver's Secret combined with its name and namespace, and it is shown in status.webhookPath. Rotating the token changes the URL, so update the webhook in your Git provider when you rotate it.