Home › Insurance and risk teams: how to use alerts.live

Insurance and risk teams

Keep a dated record of what public sources reported near insured sites or customers: civil unrest, strikes, closures and shootings, with the sources behind each alert.

What you get

• Machine-readable events through the free API (JSON or GeoJSON) with filters for place, type, confidence and time (up to 30 days back).
• Webhooks, so your own system is told when a new alert matches your filter.
• Each alert page has first and last sighting times in UTC, the sources and the confidence score, so you can store a stable link.

How to start

• Read the OpenAPI description and the developer page; a free API key raises the rate limit.
• Filter with bbox around a site, or country and city, and use min_confidence to keep only well-corroborated alerts.

Limits

• It is not a loss-adjusting or claims source. For decisions with legal effect use official records and the original publishers.
• alerts.live is descriptive and informational. It is not an official source, not an emergency service and gives no safety score for any place.
• Alerts are detected automatically in public sources and can be wrong or late. Each one shows its sources and a confidence score so you can judge it; see the methodology.
• Absence of alerts does not mean absence of events. Coverage depends on what public sources publish.

All use cases · API · Widget · Sources