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

# Creating webhooks

### [Creating an organization webhook](#creating-an-organization-webhook) <a href="#creating-an-organization-webhook" id="creating-an-organization-webhook"></a>

You can create a webhook to subscribe to events that occur in a specific organization. You must be an organization owner to create webhooks in that organization.

You can use the Shopwaive web interface or the [REST API](https://api.shopwaive.com) to create an organization webhook.&#x20;

1. Contact our team to let us know of your interest in Webhooks. We'll provide your team developer access to the Webhooks web interface after review.
2. In the upper-right corner of any page of Shopwaive, click your initial avatar.
3. Click **Settings**.
4. Scroll to **Webhooks**.
5. Click **Add webhook**.
6. Under "Payload URL", type the URL where you'd like to receive payloads.
7. Optionally, under "Secret", type a string to use as a `secret` key. You should choose a random string of text with high entropy. You can use the webhook secret to limit incoming requests to only those originating from Shopwaive. For more information, see "Validating webhook deliveries."
8. Under "Which events would you like to trigger this webhook?", select the types of webhooks you'd like to recieve. You should only subscribe to the webhook events that you need.
9. To make the webhook active immediately after adding the configuration, select **Active**.
10. Click **Add webhook**.

After you create a new webhook, Shopwaive will send you a simple `ping` event to let you know you've set up the webhook correctly. For more information, see "[Webhook events and payloads](/reference/webhook-events-and-payloads.md)."


---

# 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://webhooks.shopwaive.com/reference/creating-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.