The sandbox never delivers email or SMS — which until now meant you had no way to know a test order had produced a notification at all. It records them instead, and you can read them.
New#
GET /v1/notifications#
Every message the platform sent about your orders. Scoped by seller, not by recipient: most of this mail goes to buyers, so filtering on "addressed to you" would show you almost nothing of your own orders.
GET /v1/notifications?order_id=721&channel=mail
GET /v1/notifications/{id}#
Adds the recipient and the rendered body.
The notification.sent webhook#
Subscribe rather than poll. Thin, like every other event here — ids and a status, with the content behind the endpoint above:
{
"type": "notification.sent",
"data": {
"notification_id": 7,
"channel": "mail",
"status": "suppressed",
"template": "email_shipping_sent",
"order_id": 721
}
}
The one field to read carefully#
status: suppressed is the sandbox's normal state. The message was composed in
full and deliberately not delivered. It is not sent, and treating it as such would
have you waiting on mail that was never going to arrive.
In production the same rows carry sent or failed — and only metadata, because a
rendered order email carries the buyer's name, address and phone. body_available
tells you which you are looking at.