Changelog

Changes to the API, webhooks and MCP server that affect integrations, newest first. Data changes, such as new sources or wider coverage, are listed when they add new signal types or fields.

2026-11-18: v1#

The state of the API when these docs were published.

REST API#

  • Signals: GET /v1/signals with status, type, min_severity, country, airport, provider, since, limit and offset; GET /v1/signals/{id} with impact_forecast.
  • Signal fields include version, source.last_checked_at and source.stale. Signal ids carry a per-organisation suffix.
  • Exposure: POST /v1/exposure/check for flights, trips, places, carriers and providers, up to 500 items, with risk levels none to severe.
  • Watchlists: create, list, get, delete, add or update items, remove items, and current exposure. Flights and trips expire a day after they end.
  • Forecasts: GET /v1/forecast, GET /v1/failure-layers, GET /v1/events and GET /v1/events/{id}, with base rates, lift and above_base_rate.
  • Reference: GET /v1/airports/{iata}, GET /v1/carriers/{code}, GET /v1/providers, GET /v1/sources.
  • Account: GET /v1/plans, GET /v1/me, GET /v1/usage.
  • Limits: per-minute rate limit and monthly quota per organisation, daily record budget on list endpoints, plan page size caps.

Webhooks#

  • signal.created, .escalated, .updated, .resolved, and exposure.* events for webhooks filtered on watchlists.
  • HMAC-SHA256 Disrupt-Signature header; retries after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours; disabled after 50 consecutive failures.

MCP server#

  • Remote server at /mcp (Streamable HTTP, stateless) with 14 tools, authenticated with the API key.

Data#

  • 93 sources across aviation, weather, natural hazards, travel advisories, news-derived unrest and strikes, IT and cloud, internet, health, rocket launches and GPS interference.

Last updated 2026-11-18. Questions or a mistake on this page? Contact us.