Weather warnings API for travel, from the official weather services
DisruptAPI collects the official warnings of national weather services, through EUMETNET Meteoalarm for 38 European countries and directly from the US National Weather Service, Environment Canada and the services of Argentina, Colombia, the Philippines, New Zealand, Saudi Arabia and Taiwan. Each warning is normalised to one format and placed on the region it covers, with the airports in it. Everywhere else, airport METAR reports show severe weather as it happens.
Where the data comes from
| EUMETNET Meteoalarm (38 countries) | Official national warnings, colour-coded yellow, orange and red. |
| US National Weather Service | Every active warning, watch and advisory, placed on the counties and zones it covers. |
| Environment and Climate Change Canada | Official Canadian weather alerts. |
| National weather services (CAP) | Argentina, Colombia, the Philippines, New Zealand, Saudi Arabia and Taiwan. |
| NOAA Aviation Weather Center | METAR reports from about 5,000 airports: fog, freezing rain, snow, storms and wind. |
Every source, with its licence and polling interval, is on the data sources page.
How CAP severity maps to DisruptAPI severity
| CAP severity in the warning | DisruptAPI severity |
|---|---|
| Extreme | extreme |
| Severe | severe |
| Moderate | moderate |
| Minor | minor |
How are these signals matched to my bookings?
Warnings match on the region they cover, not the whole country. A warning for the Alps does not alert a traveller in Vienna, and a hotel or airport inside the warning area does. Send items with an exposure check or a watchlist, or receive matches by webhook.
What it does not cover
- Coverage of official warnings is limited to the services listed. Elsewhere, only airport weather observations are available.
- Warnings are passed on as issued. DisruptAPI does not make its own forecast of the weather.
What a signal looks like
Request GET /v1/signals?type=weather&country=NO&min_severity=severe. Each item in data looks like this (an example):
{
"id": "sig_19be44",
"type": "weather",
"subtype": "wind",
"provider": null,
"failure_layer": null,
"title": "Red wind warning, Western Norway",
"severity": "extreme",
"countries": [
"NO"
],
"airports": [
"BGO",
"SVG",
"HAU"
],
"areas": [
"Vestland",
"Rogaland"
],
"starts_at": "2026-11-18T06:00:00Z",
"ends_at": "2026-11-19T00:00:00Z",
"first_seen_at": "2026-11-17T14:22:03Z",
"updated_at": "2026-11-17T14:22:03Z",
"source": {
"url": "https://meteoalarm.org/",
"attribution": "EUMETNET Meteoalarm / MET Norway",
"stale": false
},
"details": {
"event": "Wind",
"awareness_level": "red"
},
"status": "active",
"version": 1,
"location": null
}Questions
Is there a Meteoalarm API?
Meteoalarm publishes feeds per country, and each one fills the CAP format in its own way. DisruptAPI reads them, normalises them and places each warning on its area, so you get one JSON format for every country.
Do I need to credit the weather services?
Yes. Each signal carries its attribution and a link to the source, and the licences of the weather services require you to keep that credit when you show the warning.
Other signal types
Hear about the disruption before your customers do
Create a key, add the flights, trips and places you want watched, and get a signed webhook whenever a disruption touches one. Try it on a sandbox key first, no card needed.