alert.refired
When Signals sends alert.refired, its payload and how to handle it in Node.js, Python and Java.
Another breach of the same trigger refreshes an open alert. A refire that carries no reading and restates the value it already held is not sent.
Payload
Every delivery is the envelope type, timestamp, sequence and data; the delivery's id is the webhook-id header. See Verify webhooks.
{
"type": "alert.refired",
"timestamp": "2026-10-25T08:00:02.000Z",
"sequence": 1043,
"data": {
"id": "0b9d7e52-1f3a-4e8c-b6a2-7c4d9e1f2a35",
"patient": "6f1c2a8e-3b7d-4c55-9a0e-2d4b8f6e1a90",
"observation": "a3e8f1c2-5d6b-4a7e-9c0f-1b2d3e4f5a6b",
"observationObservedAt": "2026-10-25T08:00:00.000Z",
"component": {
"code": {
"coding": [
{
"code": "8867-4",
"system": "http://loinc.org"
}
]
},
"valueQuantity": {
"value": 140,
"unit": "/min"
}
},
"triggerCode": "8867-4",
"triggerVersion": 1,
"value": 140,
"message": "Heart rate above 110 /min",
"reason": "trigger",
"createdAt": "2026-10-25T08:00:02.000Z",
"updatedAt": "2026-10-25T08:01:02.000Z",
"effectiveTS": "2026-10-25T08:01:00.000Z",
"observationRefId": "reading-0001",
"derivedObservation": null,
"patientRefId": "resident-001",
"episodeId": "e7a1b2c3-d4e5-4f60-8a9b-0c1d2e3f4a5b",
"acknowledgedAt": null,
"acknowledgedBy": null,
"version": 2
}
}The data fields are those of alert.triggered. effectiveTS advances on every refire, so it tells a refire from a duplicate of the same delivery.
Handle the event
Verify the delivery first (Verify webhooks), then act on the verified event as in Handle an event.
export async function handle(webhookId, event) {
if (!(await firstTime(webhookId))) return;
const { data } = event;
switch (event.type) {
case 'alert.refired':
await saveAlert(data);
break;
default:
break;
}
}Related
Last updated on