---
title: "Notification Event Status"
method: GET
path: "/v1/notifications/{event_id}"
tags: ["notifications"]
---

# Notification Event Status

`GET /v1/notifications/{event_id}`

## Request

- Base URL: `https://api.elaan.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.elaan.io/v1/notifications/{event_id}`
- Auth: none declared

Delivery status of a previously-triggered event: pending / processed /
failed, plus any per-channel error summary and the processing timestamp.

## Path parameters

- `event_id` string, required

## Headers

- `authorization` string, nullable

## Response `200`

Successful Response

- NotificationEventStatusResponse: Delivery status of a triggered event. `status` is pending/processed/failed; `error` is the failure reason (whole-event) or a per-channel failure summary on an otherwise-processed event (None when every enabled channel succeeded). `notes` is non-failure diagnostics (e.g. the named brand didn't resolve, so the default was used) — present even on a fully-successful delivery.
  - `event_id` string, required
  - `status` 'pending' | 'processed' | 'failed', required: Lifecycle of a recorded event. `PENDING` until the fan-out worker picks it up; `PROCESSED` once fan-out finished (possibly with per-channel errors noted in `last_error`); `FAILED` when the event couldn't be processed at all (the recipient / type didn't resolve, so no channel could be attempted). An unknown branding is *not* fatal — fan-out falls back to the tenant default.
  - `error` string, nullable, required
  - `notes` string, nullable, required
  - `created_at` string, date-time, required
  - `processed_at` string, date-time, nullable, required
  - `redacted` boolean: True once the recipient was erased and this event's personal data was removed. `error` and `notes` are then always null, because both quote the recipient — without this flag an integration polling a failed event would see the reason vanish and read it as a bug. A `failed` status on a redacted event may mean the trigger was cancelled by the erasure rather than that delivery failed.

## Other responses

- `404`: No triggered event with this id for this tenant
- `422`: Validation Error

---

[API](https://skmtc.dev/elaan/apis/elaan-api.md) · [All operations](https://skmtc.dev/elaan/apis/elaan-api/llms.txt) · [OpenAPI document](https://skmtc.dev/elaan/apis/elaan-api/revisions/c96a7e6399aa?raw)