search
Contact API support

Event data in webhooks

Webhooks are limited in the data they carry to remain as fast as possible. Webhook data is always contained in the JSON body of a webhook:

  • storeId Ecwid store ID.

  • eventCreated UNIX timestamp when the event happened.

  • eventId Internal ID of the webhook event. Unique for each webhook.

  • eventType Entity and action of the event defining what happened in the store. For example, the order.created event means that a new order was placed in the store.

  • entityId: ID of the affected item, such as order ID, product ID, customer ID, etc. This ID allows you to request additional details about the entity with REST API immediately after receiving a webhook.

  • data object: Additional details available to some events. For example, all order.created and order.updated webhooks always contain order payment and fulfillment statuses in addition to the order ID.

hashtag
Webhook JSON examples

Order events:

{
  "eventId":"80aece08-40e8-4145-8764-6c2f0d38678",
  "eventCreated":1234567,
  "storeId":1003,
  "entityId":103878161, // internal order ID. Use "orderId" instead
  "eventType":"order.created",
  "data":{
    "orderId":"XJ12H", // ID of created order
    "newPaymentStatus":"PAID",
    "newFulfillmentStatus":"SHIPPED"
  }
}

Abandoned cart events:

Product events:

Category events:

Product review events:

Customer events:

Application events (can only be received by the same app):

Store profile events:

Discount coupon events:

Promotion (advanced discount) events:

Invoice events:

PreviousList of webhook eventsNextPass additional data through webhooks

Last updated

Was this helpful?