Connect Webhooks

Connect webhooks are part of our automations and integrations featureset. You can subscribe to webhook events either using our API or by contacting our IT team.

The supported events to subscribe to are:

EVENT	DESCRIPTION
ORDER_CREATED	Triggered when an order is created.
ORDER_UPDATED	Triggered whenever an order is updated. Note that you should use the more specific events if you do not want to track any and all changes to orders. If you wish to track cases where orders were placed on hold, this is the endpoint to use though.
ORDER_FULFILLED	Triggered when an order is moved to pending fulfillment. The order is queued up in the fulfillment service, and ready to be picked, packed and shipped. You will note that some endpoints to not allow you to update orders once they reach this point.
ORDER_SHIPPED	The order was marked shipped, and a shipment was created for it. Note: If you wish to get a tracking number, we instead recommend using the SHIPMENT_CREATED event instead. Both of them are triggered at the same time, while this one is triggered only on the first time a shipment is created.
ORDER_CANCELLED	Order was marked as cancelled.
ORDER_SPLIT	Order was split. In case an order needs to be split shipped, an order is split into two separate orders with some items to be shipped later.
ORDER_RESHIPPED	Order was reshipped. For orders that were already shipped or cancelled, this means the order had to be shipped again, due to issues in the fulfillment/delivery process, etc.
SHIPMENT_CREATED	A Shipment was created. A shipment is the entity that holds the tracking number.
SHIPMENT_UPDATED	A shipment was updated. Note that this only happens for orders that have package tracking enabled.
SHIPMENT_RECEIVED	A shipment was received by the customer. Note that this is only supported for orders that have package tracking enabled.
SHIPMENT_CANCELLED	If a tracking number was voided, and a new one was created, this is the event that is called in those cases.
PURCHASE_ORDER_CREATED	PO was created.
PURCHASE_ORDER_UPDATED	PO was updated.
WARESHIPMENT_CREATED	Warehouse Shipment was created.
WARESHIPMENT_UPDATED	A warehouse shipment gets updated.
WARESHIPMENT_RECEIVED	When a warehouse shipment gets received by the warehouse in question
ORDERRETURN_CREATED	An Order Return was entered into the system.
ORDERRETURN_PROCESSED	A return was processed (inventory was placed into the warehouse if not damaged, or processed but as damaged).

Important

Note that webhooks events are not triggered by actions via the API. Meaning if you hit the Connect API to create an order, you will not trigger a ORDER_CREATED webhook event. But if you create an order via the Connect dashboard, you will.

The webhook handler expects the endpoint it is configured return a HTTP 200 OK response, if possible with empty content. In case we do not get that response the request will be resent up to a total of 10 times. If all fail the error will be logged.

The endpoint set will be hit with a POST request with the following JSON payload:

{
  "RequestId": "{Unique Id for the webhook request}",
  "AutomationId": "{Id for the automation configured. Is returned to you when subscribing to a webhook event via the API.}",
  "EventId": "The Event ID in question. Please look up the table above for a list of possible values. Parse the response based on this.",
  "Order": "{OrderDto - look up the schema for it in the Connect API}",
  "Shipment": "{Order ShipmentDto}",
  "WarehouseShipment": "{WarehouseShipmentDto}",
  "PurchaseOrder": "{PurchaseOrderDto}",
  "OrderReturn": "{OrderReturnDto}",
  "BulkShipment": "{BulkShipmentDto}"
}

The API schema models can be found here:

https://api.lacoreconnect.com/docs/index.html?urls.primaryName=V2