> 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/developers-guides/integration-guides/webhooks/webhooks-configure.md).

# Webhooks (Configure)

## Configure webhooks

The admin console provides a self-service way to create and manage webhooks. No API integration is required.

### Create a webhook

Open **Settings → General → Webhooks**. Create a webhook, then complete the required fields.

* **Description** identifies the webhook in the console.
* **Endpoint** is the HTTPS URL that receives webhook requests.
* **Events** defines which events trigger delivery.

The console generates an ID and a Secret automatically. The Secret is the HMAC signing key for webhook requests.

{% hint style="warning" %}
Copy the Secret immediately after creation. The full value is not shown again.
{% endhint %}

### Edit a webhook

Open **Settings → General → Webhooks**, then select the webhook to edit. Update its Description, Endpoint, or Events fields and save the changes.

Confirm that the Endpoint is reachable over HTTPS. Confirm that the selected Events match the required integration flow.

### Validate the setup

Store the Secret in the receiving system before enabling production processing. Use it to validate the `x-neostore-signature` header on every request.

For event payloads and signature validation, see [Webhooks](/developers-guides/integration-guides/webhooks.md).

### FAQ

<details>

<summary><strong>Is API access required to create a webhook?</strong></summary>

No. Webhooks can be created and managed from the admin console.

</details>

<details>

<summary><strong>Can the Secret be retrieved later?</strong></summary>

No. Copy and store the Secret when the webhook is created. The console does not show the full value again.

</details>


---

# 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/developers-guides/integration-guides/webhooks/webhooks-configure.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.