Events
Every event Zaher sends, when it fires, and what it contains.
Subscribe each endpoint to the events it needs. Full payload schemas and examples are in the Reference section of the sidebar.
Orders
data is the full order: status, totals, customer, billing and shipping
addresses, and line items. Money values are decimal strings ("149.00") in
the order's currency.
| Event | Fires when |
|---|---|
order.created | An order is placed — including unpaid (pending) orders and orders created manually in the dashboard. |
order.completed | An order is paid and completed. |
order.status_changed | An order's status changes. data.previous_status holds the old value. |
order.canceled | An order is canceled. |
order.refunded | An order is refunded. |
One change can produce several events. When an order goes from pending to
completed you receive both order.status_changed and order.completed —
subscribe to whichever fits your workflow.
Order statuses
draft, pending, pending_payment, captured, confirmed, completed,
canceled, failed, refunded.
Channels
data.channel tells you where the order came from: storefront,
marketplace, zaher or dashboard (created by hand in the dashboard).
Bookings
data is the consultation booking: date, time and timezone, duration,
meeting method and link, the related order and product, and the customer.
| Event | Fires when |
|---|---|
booking.created | A booking is created. |
booking.accepted | A booking is accepted. |
booking.canceled | A booking is canceled. |
Booking statuses
initiated, pending, accepted, canceled.
Customer data
Payloads include the customer's name, email, phone and addresses so you can fulfil orders and sync your CRM. Treat them as personal data — see Security.