> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/configure/advanced-configuration/platform/general/webhooks.md).

# Webhooks

Webhooks allow systems to receive real-time HTTP notifications whenever an event occurs in The Wallet Crew. Webhook registration is self-serve through **Settings → General → Webhooks** in the admin console. No API call is required to create or manage webhooks.

## Manage webhooks from the console

Open **Settings → General → Webhooks**. The list shows all registered webhooks, including **Description**, **Endpoint**, **Events**, and **Enabled** status.

To create or edit a webhook, open its edit form. The form contains the following fields:

* **ID** — Auto-generated and read-only. Use this value to reference the webhook through the API.
* **Secret** — The HMAC signing key used to verify deliveries. A show/hide toggle controls visibility. Store this value server-side and never expose it in client code.
* **Enabled** — Pauses or resumes delivery without deleting the webhook.
* **Description** — A label used for reference.
* **Endpoint** — The HTTPS URL that receives `POST` requests.
* **Events** — One or more event subscriptions. Use **Add event** and **Remove event** to manage the list.

## Event filter syntax

Each **Events** entry is a string. Three forms are supported:

| Syntax         | Meaning                                         |
| -------------- | ----------------------------------------------- |
| `*`            | Subscribe to all events.                        |
| `Pass:*`       | Subscribe to all events in the `Pass` category. |
| `Pass:Created` | Subscribe to one specific event.                |

Wildcards and explicit events can be combined in the same webhook. For example:

* `["Customer:*", "Pass:Created"]`
* `["Pass:*", "Redirect:Redirected"]`

## Signature validation

Every delivery includes the `x-neostore-signature` header. Validate it server-side with the webhook **Secret**. See the [Webhooks developer guide](https://docs.thewalletcrew.io/developers-guides/integration-guides/webhooks) for the full validation pattern and event payload reference.

{% hint style="warning" %}
Always validate `x-neostore-signature` on every incoming request. Do not rely solely on network IP allowlists.
{% endhint %}


---

# 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.thewalletcrew.io/configure/advanced-configuration/platform/general/webhooks.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.