Skip to main content
WEBHOOK
Requires “Customers” in API settings
This event does not fire when only order statistics or the loyalty points balance change: those fields are a snapshot of the current state, moved by the customer’s orders rather than by an edit to the customer.To follow those fields, use the order.* and loyaltylog.* events and read the customer endpoint for the current figures.

Authorizations

X-Xmenu-Signature
string
header
required

HMAC-SHA256 signature of the payload, calculated using the restaurant's Webhook Secret. See the Webhook Security documentation for validation details.

Body

application/json
event
enum<string>
required

Event type identifier

Available options:
customer.changed
action
enum<string>
required

Type of change that triggered this event:

  • created = The customer was created
  • updated = The customer's data was updated
  • deleted = The customer was removed
Available options:
created,
updated,
deleted
customer
object
required

Response

200

Return a 200 status to indicate that the webhook was received successfully