notifications

Notification Event Status

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

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

Path parameters

event_idstring required

Headers

authorizationstring nullable

Response

Successful Response

event_idstring 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.

errorstring nullable required
notesstring nullable required
created_atstring date-time required
processed_atstring date-time nullable required
redactedboolean

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.

Changes

No recorded changes to this operation across all 1 revision of this API.