> ## 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.

# Eaglecart Webhook Event Reference: Topics and Payloads

> Browse every webhook event topic fired by Eaglecart — orders, products, customers, and inventory — with sample JSON payloads for each topic.

Eaglecart fires webhooks for events across orders, products, customers, and inventory. Each event is identified by a dot-separated topic string such as `order.created` or `inventory.low_stock`. Subscribe to exactly the topics your integration needs so your endpoint only receives relevant payloads.

> [!TIP]
>
> Subscribe only to the event topics you actually need. Receiving irrelevant events adds latency to your handler, increases the risk of processing errors, and makes your delivery logs harder to read. You can always add or remove subscriptions later from **Settings → Developer → Webhooks**.

***

## Event Topics

> [accordion] Order Events
>
> Order events fire whenever the lifecycle of an order changes — from placement through fulfilment, cancellation, or refund.
>
> ### `order.created`
>
> Fired when a customer successfully places a new order. Use this event to trigger fulfilment workflows, send order confirmation emails via a third-party provider, or sync the order to an external ERP.
>
> ```json Sample payload — order.created theme={null}
> {
>   "topic": "order.created",
>   "fired_at": "2024-06-15T10:32:00Z",
>   "data": {
>     "id": "ord_01HXYZ9ABCDEF",
>     "status": "pending",
>     "currency": "USD",
>     "total_price": "149.99",
>     "customer": {
>       "id": "cust_01HXYZ1234567",
>       "email": "jane.doe@example.com"
>     },
>     "line_items": [
>       {
>         "product_id": "prod_01HXYZ7777777",
>         "variant_id": "var_01HXYZ8888888",
>         "title": "Classic Wool Sweater",
>         "quantity": 1,
>         "price": "149.99"
>       }
>     ]
>   }
> }
> ```
>
> ***
>
> ### `order.updated`
>
> Fired when one or more fields on an existing order change — for example, when a shipping address is corrected, a note is added, or the order status transitions. The payload includes the full updated order object.
>
> ```json Sample payload — order.updated theme={null}
> {
>   "topic": "order.updated",
>   "fired_at": "2024-06-15T11:05:00Z",
>   "data": {
>     "id": "ord_01HXYZ9ABCDEF",
>     "status": "processing",
>     "updated_at": "2024-06-15T11:05:00Z",
>     "note": "Please gift-wrap the item.",
>     "total_price": "149.99"
>   }
> }
> ```
>
> ***
>
> ### `order.fulfilled`
>
> Fired when an order (or a fulfilment within an order) is marked as fulfilled. The payload includes the tracking number and carrier if they were entered at the time of fulfilment.
>
> ```json Sample payload — order.fulfilled theme={null}
> {
>   "topic": "order.fulfilled",
>   "fired_at": "2024-06-16T08:14:00Z",
>   "data": {
>     "id": "ord_01HXYZ9ABCDEF",
>     "status": "fulfilled",
>     "fulfillment": {
>       "id": "ful_01HXYZ0000001",
>       "tracking_number": "1Z9999W99999999999",
>       "tracking_url": "https://www.ups.com/track?tracknum=1Z9999W99999999999",
>       "carrier": "UPS",
>       "fulfilled_at": "2024-06-16T08:14:00Z"
>     }
>   }
> }
> ```
>
> ***
>
> ### `order.cancelled`
>
> Fired when an order is cancelled, either by the merchant or by an automated rule. The payload includes the cancellation reason and who initiated it.
>
> ```json Sample payload — order.cancelled theme={null}
> {
>   "topic": "order.cancelled",
>   "fired_at": "2024-06-15T14:00:00Z",
>   "data": {
>     "id": "ord_01HXYZ9ABCDEF",
>     "status": "cancelled",
>     "cancelled_at": "2024-06-15T14:00:00Z",
>     "cancel_reason": "customer_request",
>     "cancelled_by": "merchant"
>   }
> }
> ```
>
> ***
>
> ### `order.refunded`
>
> Fired when a refund is issued against an order. The payload includes the refunded amount, the line items affected, and whether the refund was full or partial.
>
> ```json Sample payload — order.refunded theme={null}
> {
>   "topic": "order.refunded",
>   "fired_at": "2024-06-17T09:22:00Z",
>   "data": {
>     "id": "ord_01HXYZ9ABCDEF",
>     "refund": {
>       "id": "ref_01HXYZ0000002",
>       "amount": "149.99",
>       "currency": "USD",
>       "reason": "Item arrived damaged",
>       "refund_type": "full",
>       "refunded_at": "2024-06-17T09:22:00Z"
>     }
>   }
> }
> ```

> [accordion] Product Events
>
> Product events fire when items in your product catalogue are created, modified, or removed. Subscribe to these events to keep external search indexes, product feeds, or warehouse systems in sync.
>
> ### `product.created`
>
> Fired when a new product is published or saved to the catalogue for the first time.
>
> ```json Sample payload — product.created theme={null}
> {
>   "topic": "product.created",
>   "fired_at": "2024-06-10T13:00:00Z",
>   "data": {
>     "id": "prod_01HXYZ7777777",
>     "title": "Classic Wool Sweater",
>     "handle": "classic-wool-sweater",
>     "status": "active",
>     "vendor": "Woolmark Co.",
>     "product_type": "Apparel",
>     "variants": [
>       {
>         "id": "var_01HXYZ8888888",
>         "title": "Medium / Navy",
>         "sku": "CWS-M-NVY",
>         "price": "149.99",
>         "inventory_quantity": 42
>       }
>     ],
>     "created_at": "2024-06-10T13:00:00Z"
>   }
> }
> ```
>
> ***
>
> ### `product.updated`
>
> Fired when any field on a product or one of its variants changes — including price, description, images, or stock levels updated through the product editor.
>
> ```json Sample payload — product.updated theme={null}
> {
>   "topic": "product.updated",
>   "fired_at": "2024-06-11T15:30:00Z",
>   "data": {
>     "id": "prod_01HXYZ7777777",
>     "title": "Classic Wool Sweater",
>     "updated_at": "2024-06-11T15:30:00Z",
>     "variants": [
>       {
>         "id": "var_01HXYZ8888888",
>         "price": "129.99",
>         "compare_at_price": "149.99"
>       }
>     ]
>   }
> }
> ```
>
> ***
>
> ### `product.deleted`
>
> Fired when a product is permanently deleted from the catalogue. Note that archiving a product does **not** fire this event; it fires `product.updated` with `"status": "archived"`.
>
> ```json Sample payload — product.deleted theme={null}
> {
>   "topic": "product.deleted",
>   "fired_at": "2024-06-12T09:00:00Z",
>   "data": {
>     "id": "prod_01HXYZ7777777",
>     "deleted_at": "2024-06-12T09:00:00Z"
>   }
> }
> ```

> [accordion] Customer Events
>
> Customer events fire when shopper accounts are created, updated, or removed. Use these to sync customer records to a CRM, marketing platform, or loyalty programme.
>
> ### `customer.created`
>
> Fired when a new customer account is created, either by the customer registering on the storefront or by the merchant creating one manually in the admin.
>
> ```json Sample payload — customer.created theme={null}
> {
>   "topic": "customer.created",
>   "fired_at": "2024-06-14T18:45:00Z",
>   "data": {
>     "id": "cust_01HXYZ1234567",
>     "email": "jane.doe@example.com",
>     "first_name": "Jane",
>     "last_name": "Doe",
>     "phone": "+15035550123",
>     "accepts_marketing": true,
>     "created_at": "2024-06-14T18:45:00Z"
>   }
> }
> ```
>
> ***
>
> ### `customer.updated`
>
> Fired when a customer updates their profile information — such as their email address, password, default shipping address, or marketing preferences.
>
> ```json Sample payload — customer.updated theme={null}
> {
>   "topic": "customer.updated",
>   "fired_at": "2024-06-15T20:10:00Z",
>   "data": {
>     "id": "cust_01HXYZ1234567",
>     "email": "jane.doe@example.com",
>     "updated_at": "2024-06-15T20:10:00Z",
>     "accepts_marketing": false,
>     "default_address": {
>       "line1": "456 Oak Avenue",
>       "city": "Seattle",
>       "state": "WA",
>       "zip": "98101",
>       "country": "US"
>     }
>   }
> }
> ```
>
> ***
>
> ### `customer.deleted`
>
> Fired when a customer account is permanently deleted. This can occur when the merchant deletes the account from the admin or when a customer submits a data deletion request (GDPR/CCPA).
>
> ```json Sample payload — customer.deleted theme={null}
> {
>   "topic": "customer.deleted",
>   "fired_at": "2024-06-18T11:00:00Z",
>   "data": {
>     "id": "cust_01HXYZ1234567",
>     "deleted_at": "2024-06-18T11:00:00Z"
>   }
> }
> ```

> [accordion] Inventory Events
>
> Inventory events fire when stock levels change or fall below a critical threshold. Subscribe to these events to automate reordering, update external warehouse systems, or alert operations teams.
>
> ### `inventory.updated`
>
> Fired whenever the stock quantity of a variant changes — due to a sale, a manual adjustment in the admin, a stock receive, or a return.
>
> ```json Sample payload — inventory.updated theme={null}
> {
>   "topic": "inventory.updated",
>   "fired_at": "2024-06-15T10:33:00Z",
>   "data": {
>     "variant_id": "var_01HXYZ8888888",
>     "product_id": "prod_01HXYZ7777777",
>     "sku": "CWS-M-NVY",
>     "location_id": "loc_01HXYZSTORE01",
>     "previous_quantity": 42,
>     "updated_quantity": 41,
>     "reason": "sale",
>     "updated_at": "2024-06-15T10:33:00Z"
>   }
> }
> ```
>
> ***
>
> ### `inventory.low_stock`
>
> Fired when the available stock of a variant drops to or below its configured reorder point. Set each variant's reorder point in **Products → \[product] → \[variant] → Inventory → Reorder point**.
>
> ```json Sample payload — inventory.low_stock theme={null}
> {
>   "topic": "inventory.low_stock",
>   "fired_at": "2024-06-20T14:55:00Z",
>   "data": {
>     "variant_id": "var_01HXYZ8888888",
>     "product_id": "prod_01HXYZ7777777",
>     "sku": "CWS-M-NVY",
>     "location_id": "loc_01HXYZSTORE01",
>     "current_quantity": 5,
>     "reorder_point": 5,
>     "updated_at": "2024-06-20T14:55:00Z"
>   }
> }
> ```


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