Review-requested reminder

Sent BY Ewity TO your registered webhook URL. All events
POST to the same URL — the path on this page is for grouping
in the docs only. Identify the event by the X-Event header.

Fires when an order has been sitting in review-requested for too
long (the merchant proposed edits, the customer hasn't acted yet)
and a reminder is due. Use it to nudge the customer to open the
order and accept or cancel the merchant's changes.

The body is the full Order; its
status will always be review-requested and reminder_count
reflects how many reminders have already been sent.

How to use it

  • Surface a reminder UI on your side ("the merchant is waiting on
    you to confirm changes").
  • The customer-driven transition back to pending (i.e. accepting
    the merchant's changes) is exposed at
    POST /orders/{id}/status-change/pending.
    cancelled is the alternative.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
int64
string
online_location
object

An online location ("storefront"). Use id as online_location_id /
locationId in subsequent calls.

customer
object
string

Display label ("Delivery", "Pickup", ...) — not the input enum value.

string | null

Display label for the payment method selected at checkout. For
orders created via this API there is no checkout-time payment
method, so this field is always null on platform-created
orders. Record what you collected from the customer via
POST /orders/{id}/payment after the merchant accepts the order.

string | null
string | null

Set by the merchant when reviewing or editing the order.

string
enum
string
boolean

True only when cumulative payments on the bill cover the bill
total. Stays false for partial payments.

double
integer
lines
array of objects
lines
total_components
array of objects
total_components
online_payments
array of objects

Online payment options the customer can settle this order with,
as configured on the merchant's account. Empty for most platform
integrations (you'd typically collect payment yourself and call
POST /orders/{id}/payment); only relevant if you want to hand
the customer off to one of Ewity's online payment flows.

Each entry has a key you can pass to a settlement endpoint
(e.g. payment_key on POST /orders/{id}/payment/bank-transfer
for type: bank_transfer entries). Other type values are
handled through Ewity-managed flows that aren't exposed in this
doc set — contact [email protected] if you need them.

online_payments
payments
array of objects

Payments recorded against the order's bill. Empty until the
merchant accepts the order (no bill yet).

payments
date-time
string
extra
object
Headers
string
enum
required

Always ReviewRequestedReminder for this event.

Allowed:
Response
2XX

Receiver acknowledged.

Language
Credentials
Bearer
token
LoadingLoading…
Response
Click Try It! to start a request and see the response here!