> For the complete documentation index, see [llms.txt](https://docs.ggwp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ggwp.com/webhooks.md).

# Webhooks

## **Introduction**

Webhooks provide a way for applications to carry out near real-time information updates. These HTTP callbacks offer a mechanism for data to be delivered to other applications as soon as it is available, making them a key component in modern, interactive applications.

In the context of GGWP, webhooks can be configured to trigger on certain events. When these events occur, the server makes an HTTP request to the URL configured for the webhook. This request contains information about the event, allowing the receiving system to react accordingly. This technology allows GGWP to integrate smoothly with external services, extending functionality and facilitating near real-time updates.

A series of such webhooks are available to support automated moderation through GGWP platform. These webhooks can provide warnings when player has just begun toxic behavior or notify moderators when status of a player has changed, i.e., sanctioned or reinstated to active. Some webhooks also help in the workflow of an incident.

## **Getting Started**

1. Review [Webhook Events](/webhooks/webhook-events.md) and identify the events of interest
2. [Create URLs](/webhooks/receiving-events.md#creating-the-target-urls) to handle the selected events
3. Create the [subscriptions](https://docs.ggwp.com/pages/83sgbXcCKJTPPxXk8EQS#id-1.-subscribe-to-an-event) for the events of interest
4. Persist the received [ID and secret key](#user-content-fn-1)[^1] upon subscription creation

   a. ID can be used to manage the [subscription](/webhooks/subscriptions-apis.md#apis)

   b. Secret key is used to [validate the incoming request](/webhooks/receiving-events.md#request-validation) via HMAC

[^1]: The ID and secret key for each subscription would be unique.