DisruptAPI developer docs
DisruptAPI tells you which live disruptions touch the flights, trips, places and suppliers you care about, and what similar past events did to travel. These docs cover the REST API under /v1, signed webhooks and the MCP server for AI assistants.
What does the API do?#
DisruptAPI collects disruption reports from 93 official and open sources: FAA airport programs, national weather warnings, natural hazard alerts, government travel advisories, news-derived unrest and strikes, health notices, rocket launches, GPS interference and cloud or SaaS status pages. Each report becomes a signal with one shape, one severity scale and a link to its source.
You can read signals directly, or send the things you care about and let the API match them for you. It does not report the status of individual flights.
Core concepts#
- Signal
- One disruption from one source: a ground stop at SEA, a red wind warning in Mallorca, an incident on Cloudflare's status page. It has a type, a severity (
minortoextreme), a time window, affected countries and airports, a status (activeorresolved) and a version that goes up when it changes. - Item
- Something you want checked, with your own
id: aflight, atrip, aplace(airport, coordinates with a radius, or country; hotels and venues are places), acarrieror aprovideryour systems depend on. - Exposure
- The result of matching items to active signals: for each item, the signals that touch it, the reasons in plain words and a risk level (
none,low,elevated,high,severe). - Watchlist
- A saved list of items. Every new or changed signal is checked against it, and a webhook can tell you when one of your items is touched.
- Forecast
- For IT outages: how often comparable past events led to cancellations, check-in problems or website outages, with an 80% interval and
n, the number of past events behind each number.
Should I use REST, webhooks or MCP?#
Most integrations use REST and webhooks together: a watchlist that you keep in sync with your bookings over REST, and a webhook that tells you when one of them is exposed.
| Use | When | Start with |
|---|---|---|
| REST API | You ask a question now: is this booking exposed, what is active at this airport, what does history say about this outage. | POST /v1/exposure/check, GET /v1/signals, GET /v1/airports/{iata} |
| Webhooks | You want to be told when something starts, gets worse, changes or ends, without polling. | POST /v1/webhooks with filters, or with "watchlists": ["*"] for your own items |
| MCP server | An AI assistant or agent should answer travel disruption questions with live data. | Connect a client to /mcp with your API key; 14 tools |
What does a response look like?#
Every successful response is JSON with the result in data. Lists add a meta block with total, limit and offset. Errors use the same envelope everywhere: {"error": {"code": "...", "message": "..."}}. This is one signal from GET /v1/signals:
{
"data": [
{
"id": "faa_ground_stop_SEA.k3j9x2m1qa",
"type": "aviation",
"subtype": "ground_stop",
"provider": "faa",
"failure_layer": null,
"failure_layer_label": null,
"title": "Ground Stop Program at SEA: low ceilings",
"severity": "severe",
"status": "active",
"countries": ["US"],
"airports": ["SEA"],
"areas": [],
"location": { "lat": 47.449, "lon": -122.309 },
"starts_at": null,
"ends_at": null,
"first_seen_at": "2026-11-18T06:52:10Z",
"updated_at": "2026-11-18T07:20:41Z",
"version": 2,
"source": {
"url": "https://nasstatus.faa.gov/",
"attribution": "FAA NAS Status",
"last_checked_at": "2026-11-18T07:21:02Z",
"stale": false
},
"details": { "reason": "low ceilings", "End_Time": "8:30 am PST" }
}
],
"meta": { "total": 1, "limit": 50, "offset": 0 }
}Base URL and formats#
- Base URL:
https://app.disruptapi.com. The REST API lives under/v1, the MCP server at/mcp, the console at/console. - Authentication: an API key in
Authorization: Bearer dk_live_...orX-API-Key. See Authentication. - Times are ISO 8601 in UTC, for example
2026-11-18T07:20:41Z. Airport codes are IATA, airline codes are IATA, country codes are ISO 3166-1 alpha-2. - Request bodies are JSON, at most 2 MB.
- The machine-readable spec is at
/openapi.json, with an interactive view at/docson the API host.
Where to go next#
Get started#
Concepts#
Integrate#
Reference#
Last updated 2026-11-18. Questions or a mistake on this page? Contact us.