One notification, with its content
GET/v1/notifications/{id}
scope orders.read
Adds the recipient and the rendered body. body_available is false in production, where only metadata is kept — a rendered order email carries the buyer's name, address and phone. The sandbox has no real buyers, so it keeps everything.
Response#
| Field | Type | Description |
|---|---|---|
data | object | One delivery, with the body. |
data. | integer | The delivery id. |
data. | string | Which channel it went on. Accepts |
data. | string | What happened to it. suppressed throughout the sandbox.Accepts |
data. | integer|null | Which order it concerns. |
data. | string|null | The stable key for this message type. |
data. | string|null | Subject line, for mail. |
data. | string|null | The address or phone number it was addressed to. |
data. | string|null | Which service carried it. |
data. | string|null | The message itself — HTML for mail, plain text for SMS. null when the body was not retained. |
data. | boolean | Whether body holds anything. Check this rather than testing body for emptiness: a genuinely empty body and a body we did not keep are different facts. |
data. | string | ISO-8601 UTC. |
Example
{
"data": {
"id": 7,
"channel": "mail",
"status": "suppressed",
"order_id": 721,
"template": "email_shipping_sent",
"subject": "Comanda ta a fost expediata",
"recipient": "[email protected]",
"driver": "mailing-service",
"body": "<p>AWB 123456</p>",
"body_available": true,
"created_at": "2026-09-12T07:58:14Z"
}
}