Travel disruption data for insurers and assistance companies

Travel insurers and assistance companies use DisruptAPI to check whether a disruption happened, when it started, where it applied and how severe the issuing authority rated it. Each record keeps its official source, issue time and severity, and the catalogue of past events shows what similar disruptions did to travel.

What goes wrong today

Claims handlers spend minutes per claim searching news and weather sites to confirm a storm or a strike, and the evidence they find is hard to file.

Pricing a product for a destination needs history: how often does this airport see cancellations in this month?

Put these on a watchlist

Policies in forceTrips with dates, to reach policyholders before they travel.
ClaimsAn airport, a date range and a place to check against the record.
DestinationsCountries for advisories and health notices.

What you get from DisruptAPI

Evidence with provenance

Every signal carries its issuing authority, a link to the source, the start and end time and the official severity.

History for pricing

Monthly airport base rates (US, from BTS) and a growing catalogue of past events with measured outcomes.

Assistance before the claim

Watch policies in force and contact travellers whose trip is about to be hit.

What you send

A policy in force, checked for severe and extreme signals only.

GET /v1/signals?since=…&airport=…GET /v1/eventsGET /v1/airports/{iata}

No developer yet? Paste the same thing as CSV in the console and see results straight away.

{
  "items": [
    { "id": "POL-55120", "kind": "trip", "origin": "JFK", "destination": "MIA",
      "depart_at": "2026-11-16T13:00:00Z", "return_at": "2026-11-23T18:00:00Z" }
  ],
  "min_severity": "severe"
}

Questions from travel insurers and assistance

Can I use DisruptAPI data as evidence in a claim decision?

DisruptAPI records what official sources published and when. It links to the original so a handler can confirm it. Your claims policy decides how that evidence is used.

How far back does history go?

US flight outcomes from BTS go back years and grow with each monthly release. Live signals are kept from the day we started collecting each source. Enterprise plans include history exports.

Do you cover parametric triggers?

Signals have a stable id, a severity and exact times, which is what a parametric rule needs. Talk to us about the thresholds you use.

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.