> 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/about-webhooks-for-organizations.md).

# About webhooks for organizations

### [About webhooks for organizations](#about-webhooks-for-repositories) <a href="#about-webhooks-for-repositories" id="about-webhooks-for-repositories"></a>

Organization webhooks allow you to receive HTTP `POST` payloads whenever certain events happen from an organization, web entity, or brand website. You can use the [REST API](https://api.shopwaive.com) to manage organization webhooks. You can list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service. You can also use the REST API to change the configuration of the webhook. For example, you can modify the payload URL, content type, SSL verification, and secret.&#x20;

#### [Receiving Webhooks](#receiving-webhooks) <a href="#receiving-webhooks" id="receiving-webhooks"></a>

In order for Shopwaive to send webhook payloads, your server needs to be accessible from the Internet. We also highly suggest using SSL so that we can send encrypted payloads over HTTPS.

#### [Webhook headers](#webhook-headers)

Shopwaive will send along several HTTP headers to differentiate between event types and payload identifiers. See [webhook headers](/reference/webhook-events-and-payloads.md#delivery-headers) for details.

#### &#x20;<a href="#delivery-headers" id="delivery-headers"></a>

##


---

# 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/about-webhooks-for-organizations.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.