> 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/revealing-a-webhooks-secret.md).

# Revealing a webhook's secret

Revealing a webhook's secret is crucial for developers and administrators working with webhooks in Global Commerce. The secret is a unique token to secure communications between the webhook service and your application. This guide will walk you through retrieving your webhook's secret from the Global Commerce platform, ensuring your integration is secure and functioning correctly. Follow the steps below to reveal your webhook's secret.

To reveal a webhook's secret, you need to retrieve your endpoint's secret from the Webhook Service settings in Global Commerce:

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. \ <img src="/files/-MfYkGIdl9jGNxOzb4zn" alt="" data-size="original">&#x20;
3. Find the webhook with the secret you want to verify and click the **Reveal Secret** link.

   The Reveal Secret dialog appears.\
   &#x20;<img src="/files/-MfYyTr0GCt6FouvWc1E" alt="" data-size="original">&#x20;
4. Provide your Global Commerce username and click **Reveal**. The **Reveal Secret** field under **Secret** will display the token. 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/revealing-a-webhooks-secret.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.
