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

# Webhooks

Send OrderEazi events to your own systems as they happen, and track every delivery.

Your other systems often need to know straight away when something changes, such as an order being dispatched or a stock level changing. A webhook in OrderEazi sends a message to an address in your system, called an endpoint, each time a chosen event happens. The **Webhooks** screen lists your endpoints, and every delivery, so you can see what was sent and resend anything that failed.

### Before you start

You'll need the **Webhooks** permission, in the **Integrations** permission group. If you don't have it, ask your OrderEazi administrator to add it to your role. You'll also need the endpoint's address. Your developer sets the endpoint up.

### How to add a webhook

1. In the main menu, go to **Integrations** > **Webhooks**.
2. Select **Add Webhook**.
3. Under **Event**, choose what should trigger it, such as an order being dispatched.
4. Enter the **Destination Url**, a full https address such as <https://example.com/hooks/orders>.
5. Select **Add Webhook**.

You see the event "now posts to" the address. From then on, each time the event happens, OrderEazi sends the details to that address. A new webhook can take up to a minute to start.

### How deliveries work

Your system answers each message to say whether it got it:

* **It got it:** The delivery shows as **Delivered**.
* **It didn't answer, or had an error:** OrderEazi tries again, up to 3 more times. After that, the delivery shows as **Failed**.
* **It refused the message:** If your system says the message itself can't be used, OrderEazi doesn't try again.

### How to check and resend deliveries

The **Queue** tab lists every delivery, with its **Event**, **Destination**, **Status**, **Last Response**, and **Retries**.

1. In the main menu, go to **Integrations** > **Webhooks**, and select the **Queue** tab.
2. Filter by **Delivered**, **Retrying**, **Failed**, or **Pending**, or search for a project or order number.
3. Select a delivery to see your system's response and the message that was sent.
4. To send it again, select **Resend**, then **Resend** again to confirm.

The cards at the top show how many deliveries succeeded in the last 24 hours, how many are waiting to retry, and how many have stopped retrying.

**Example:** You add a webhook that sends dispatched orders to your shop. One afternoon your shop is down, and 5 deliveries show as **Failed**. Once it's back, you filter the **Queue** by **Failed**, open each delivery, and select **Resend**. Your shop gets the 5 dispatch updates and emails its customers.

### How to change or remove a webhook

In the main menu, go to **Integrations** > **Webhooks**. On the **Endpoints** tab, open the menu on the webhook's row:

* **Edit:** Change the event or address, and select **Save changes**.
* **View Deliveries:** Opens the **Queue**, filtered to this webhook.
* **Delete:** Stops sending, after you confirm "Yes, delete it". Deliveries for it that haven't gone out yet aren't sent.

### Related pages

* [Integrations](/central/order-management/integrations.md): the other connections
* [API Keys](/central/order-management/integrations/api-keys.md): let your system read and write data too