Unique UUID generated for this specific alarm event delivery.
registrationId
string
UUID of the alarm registration that produced this delivery.
recipientId
string
Caller-supplied identifier that ties the notification back to your internal customer/asset record (no need to use human-readable values — hashed/anonymous IDs are fine for GDPR compliance); keep it unique per monitoring point because only one registration per recipientId is allowed for the same location, letting you route the alert without storing our registrationId.
notificationTime
string
ISO-8601 date-time (UTC) of when the alarm notification was dispatched (e.g. 2025-09-14T04:00:15.123).
latitude
number
WGS84 latitude of the monitoring point. ADMINISTRATIVE: centroid of the registered district. POINT: the exact latitude supplied when the alarm was registered.
longitude
number
WGS84 longitude of the monitoring point. ADMINISTRATIVE: centroid of the registered district. POINT: the exact longitude supplied when the alarm was registered.
cityId
number
Numeric identifier of the city (province). ADMINISTRATIVE: the city ID supplied at registration. POINT: the city ID of the district whose forecast covers the registered coordinate.
city
string
Human-readable city name. Populated for ADMINISTRATIVE registrations; null for POINT registrations.
districtId
number
Numeric identifier of the district. ADMINISTRATIVE: the district ID supplied at registration. POINT: the district ID of the district whose forecast covers the registered coordinate.
district
string
Human-readable district name. Populated for ADMINISTRATIVE registrations; null for POINT registrations.
distance
number
Meters between the registered monitoring point and the district centroid used for forecast evaluation. For ADMINISTRATIVE registrations this value is effectively zero; for POINT registrations it reflects how far the registered coordinate is from the nearest district centroid.
violations
array
One entry per metric that breached the configured threshold; a single alarm can bundle multiple metrics simultaneously.
ISO-8601 timestamp (UTC) of the forecast time slot.
forecasts[].value
number
Forecast value for the metric in the units specified by violations[].unit.
1
Identify the monitoring point 🔍
Use registrationId or recipientId to look up which of your assets or customers this alarm concerns — pair it with city / district for a quick human-readable summary.
2
Triage violations ⚠️
Iterate over violations and map each metric to your internal risk policies. A single alarm can bundle multiple metrics (e.g. simultaneous heavy rain and strong gusts), so evaluate each entry independently.
3
Trigger downstream automation 🤖
Use forecasts[].time to schedule time-boxed actions — for example, send a heads-up notification at T-3h before the first threshold breach, and escalate if value keeps climbing across consecutive slots.
