> 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/enabling-or-disabling-webhooks.md).
# Turning webhooks on or off
Managing webhooks is crucial to maintaining the functionality and security of your Global Commerce integrations. This guide will walk you through the steps to turn webhooks on or off, allowing you to control how your application interacts with external services. Whether you're looking to pause webhook activity temporarily or reactivate it to resume operations, these instructions will ensure you can easily adjust your settings through the Webhook Service page.
Webhooks are automated messages sent from apps when something happens. They have a message—or payload—and are sent to a unique URL, essentially functioning as a simple way for apps to communicate and share data in real-time. This makes them an integral tool for extending and customizing the functionality of your Global Commerce integrations, enabling real-time data synchronization and automated workflows between your application and external services.
To turn webhooks on or off:
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.\
3. Select the **Webhook ID** you want to turn on or off from the list and click **Enable/Disable**.
4. From the **Webhook Status Change** dialog, enter your Global Commerce username in the field and click **Proceed**. Note that the **Username** field is case-sensitive. The **Secret** column displays the endpoint's secret.\ 
---
# 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/enabling-or-disabling-webhooks.md?ask=&goal=
```
`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.