post
https://yourplatform.com/ewity-webhook/order-status-changed
Sent BY Ewity TO your registered webhook URL. All events
POST to the same URL you registered with Ewity — the path on
this page is for grouping in the docs only. Identify the event
by theX-Eventheader.
Fires every time the order's status changes. This is the event
you'll care about most — it covers merchant acceptance (the moment
a bill is generated and POST /orders/{id}/payment becomes
callable), all forward transitions, cancellations, and the
merchant-driven "review requested" flow.
Triggering transitions:
pending→acknowledged(merchant has seen the order)acknowledged→accepted(bill generated here)accepted→ready-for-pickupready-for-pickup→on-deliveryon-delivery→completed- any state →
cancelled - any state →
review-requested(merchant proposed edits)
How to use it
- Watch for
status === "accepted"to know that a bill now exists
andPOST /orders/{id}/paymentis callable. - Watch for
status === "review-requested"if you expose
merchant-edit confirmations to the customer — see
Change Order Status for the
customer-drivenpendingtransition that completes that flow. cancelledandcompletedare terminal — stop polling /
archive on your side.- Dedupe by
(id, status); the same tuple may be delivered more
than once.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
2XXReceiver acknowledged. Anything in the 2xx range is treated
as successful delivery; non-2xx is logged as a failure.