> ## Documentation Index
> Fetch the complete documentation index at: https://help.eaglecart.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up Courier Webhooks for Automatic Delivery Updates in Eaglecart

> Set up the Jeebly webhook in Eaglecart by sending your Webhook URL and Security Key to Jeebly, check that updates arrive, and fix missing delivery updates.

[Help Center](https://help.eaglecart.com/introduction.md)

[Shipping and delivery](https://help.eaglecart.com/shipping-delivery.md)

Set up courier webhooks

# Set up courier webhooks

A webhook lets a courier tell Eaglecart when a parcel moves. When it works, the order's fulfillment status updates on its own as the courier picks up, delivers or returns the parcel.

Today, **Jeebly** is the courier with a webhook. **GetGive** has no webhook, so GetGive shipments are always updated by hand.

| Courier | Webhook | Delivery updates |
| - | - | - |
| **Jeebly** | Yes, in **Webhook Configuration** on its setup page | Automatic once Jeebly sets up the webhook |
| **GetGive** | No | Manual. You update the fulfillment status on the order. |

## Before you start

* Connect Jeebly first and click **Save**. The Security Key only appears after a successful save. See [Connect Jeebly](https://help.eaglecart.com/shipping-delivery/connect-jeebly.md).
* Know who your Jeebly account manager is. The webhook is set up on Jeebly's side, not in Eaglecart.

## How the Jeebly webhook works

The **Webhook Configuration** section explains it: it lets Jeebly automatically notify Eaglecart when parcels are picked up, delivered or returned, which keeps fulfillment status updated without manual action.

Two values make it work:

* **Webhook URL:** the address Jeebly sends shipment updates to. The page says Jeebly sends shipment updates to this URL, and the system updates the status automatically.
* **X-API-KEY / Security Key:** a private key Eaglecart generates for your store. Jeebly sends it back with every update, so Eaglecart knows the update really came from Jeebly.

## Set up the Jeebly webhook

1. Go to **Settings → Couriers → Jeebly**.
2. Make sure your account details are saved. Before you save, **X-API-KEY / Security Key** shows "Not added yet" with the note "Save your Jeebly account details above and your key will appear here."
3. In **Webhook Configuration**, click the copy button next to **Webhook URL**.
4. Copy the **X-API-KEY / Security Key** with its copy button. Use the eye icon if you want to see it.
5. Send both values to your Jeebly account manager and ask them to set up the webhook on your account.
6. When Jeebly confirms, check the status pill at the top right of the section.

> [!WARNING]
>
> The Security Key works like a password. Only share it with your Jeebly account manager, never in public channels or screenshots.

> [!NOTE]
>
> Opening the Webhook URL in your browser doesn't turn anything on. Updates only start once Jeebly adds both values to your account.

## Check that updates are arriving

The status pill in **Webhook Configuration** shows:

| Status | Meaning |
| - | - |
| **Not receiving yet** | No updates have arrived from Jeebly. The webhook may not be set up yet, or not correctly. |
| **Receiving updates** | Jeebly is sending updates. Below the key you'll also see when the last one arrived, for example "Last update received 1 Sep, 2026 at 6:31 PM". |

You can also open a Jeebly order that's been handed over and check its **Order history**. Courier updates appear there as fulfillment changes.

## What updates change

With the webhook working, Jeebly's delivery events can move an order to:

* **In Transit**
* **Out for Delivery**
* **Delivered**
* **Return to Origin**

Each update is recorded in the order's history, and supported updates also show on the customer's order tracking. Statuses before that, such as **Ready for Dispatch** (set when you create the shipment) and **Handover to Courier** (set with **Hand Over To Courier**), come from your own actions. See [Automatic shipment status updates](https://help.eaglecart.com/shipping-delivery/automatic-status-updates.md).

## Diagnose missing updates

**The pill says Not receiving yet.**
Jeebly hasn't sent any updates. Send the Webhook URL and Security Key to your Jeebly account manager again and ask them to confirm the webhook is set up on your account.

**The pill says Receiving updates, but one order hasn't moved.**
Check that the order was booked with Jeebly through Eaglecart. Orders with custom tracking never receive courier updates, even if the parcel went with Jeebly. Also check the order's history for recent courier entries; the parcel may simply not have moved yet.

**The last update is old.**
Compare the "Last update received" date with your recent shipments. If you've handed over parcels since then and nothing has arrived, ask Jeebly to check the webhook.

**I changed my Jeebly keys.**
After saving new account details, check that the Webhook URL and Security Key Jeebly has still match the values shown on the page. If they differ, send the current values to Jeebly.

**Shipments book fine, so isn't the courier connected?**
Booking and delivery updates are separate. Your keys let Eaglecart book shipments; the webhook lets Jeebly report back. One can work without the other.

**My GetGive orders don't update.**
That's expected. GetGive has no webhook. Update the order's fulfillment status yourself when GetGive confirms delivery.

## Related guides

* [Connect Jeebly](https://help.eaglecart.com/shipping-delivery/connect-jeebly.md): account details and pickup address.
* [Connect GetGive](https://help.eaglecart.com/shipping-delivery/connect-getgive.md): GetGive setup and manual status updates.
* [Automatic shipment status updates](https://help.eaglecart.com/shipping-delivery/automatic-status-updates.md): which statuses change on their own.
* [Track a shipment](https://help.eaglecart.com/shipping-delivery/track-a-shipment.md): how tracking appears to you and your customers.
* [Order history](https://help.eaglecart.com/orders/order-history.md): where courier updates are recorded.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.