> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api/events/webhooks/searching-for-a-webhook.md).

# Searching for a webhook

Searching for an existing webhook in Global Commerce is a simple process that allows you to locate and manage your webhooks quickly. This feature is especially valuable when you need to review or modify the settings of a specific webhook. Follow the steps outlined below to find a webhook using its unique ID.

To search for an existing webhook:

1. Sign in to [Global Commerce](https://gc.digitalriver.com/gc/ent/login.do).
2. Select **Administration**, and then click **Webhook Service**. The Webhook Service page appears.\
   &#x20;<img src="/files/-MfYkGIdl9jGNxOzb4zn" alt="" data-size="original">
3. Type the webhook's real ID in the **Webhook ID** field on the Webhook Service page and click **Search**. A webhook ID only appears in the search results if it matches the text you type in the **Search** field.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/commerce-api/events/webhooks/searching-for-a-webhook.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.