cURL
Notifications
Retrieve notification
Retrieve a single notification by its id.
Sending is asynchronous: the send endpoint accepts the notification and returns its id with status: "enqueued", then a worker resolves in-app delivery and — when the send included an email block — the email. Poll this endpoint to read the resolved in-app status and the email delivery outcome on email (whether it was sent, delivered, bounced, …).
GET
cURL
Retrieve a single notification by the
id returned from send a notification.
Because sending is asynchronous, this is how you learn what actually happened to a send:
status— the in-app outcome.enqueuedright after the send, thendelivered,muted(preferences disallow),quota_exceeded, orfailed.email— the email outcome, present only when the send included anemailblock. It has its own lifecycle:pending→sent(provider accepted) →delivered/bounced/complained(from provider webhooks), orfailed/muted/no_contact.
Authorizations
Bearer authentication header of the form Bearer bv_xxxxxxxxx, where bv_xxxxxxxxx is your API Key with Full access scope.
Path Parameters
The unique identifier of the notification (the id returned by the send endpoint).
Response
Notification found