Sources may want to correlate sent notifications with their own history. To allow this, the HTTP API must provide a new endpoint by which it is possible to fetch notifications sent since a given time:
GET /notifications?since=<timestamp>
A source is always expected to pass a timestamp, even if that's just the current time.
The API responds with a single line of JSON for each entry. Each entry is separated by a new line.
Each entry has the property event_id which is the unique identifier provided by the source when delivering the event. (See #394)
There may be notifications sent due to an escalation that isn't itself triggered by an event. Such must have the event id of the most recent severity change.
Only sent notifications. i.e. unless the notification has been attempted to deliver, no entry is returned.
{
"event_id": "a554df8b…",
"sent_at": 123456,
"contact_name": "John Doe",
"contactgroup_name": "The Does",
"schedule_name": "Everyday",
"channel_name": "Mail",
"message": "Something gone wrong."
}
Sources may want to correlate sent notifications with their own history. To allow this, the HTTP API must provide a new endpoint by which it is possible to fetch notifications sent since a given time:
GET /notifications?since=<timestamp>A source is always expected to pass a timestamp, even if that's just the current time.
The API responds with a single line of JSON for each entry. Each entry is separated by a new line.
Each entry has the property
event_idwhich is the unique identifier provided by the source when delivering the event. (See #394)There may be notifications sent due to an escalation that isn't itself triggered by an event. Such must have the event id of the most recent severity change.
Only sent notifications. i.e. unless the notification has been attempted to deliver, no entry is returned.
{ "event_id": "a554df8b…", "sent_at": 123456, "contact_name": "John Doe", "contactgroup_name": "The Does", "schedule_name": "Everyday", "channel_name": "Mail", "message": "Something gone wrong." }