Australia’s official data feeds, in one API.

Incidents, warnings, disaster declarations and river gauges from 34 official state and federal sources, normalised into a single schema and kept current. Integrate once instead of maintaining a scraper per agency.

Get an API key Read the docs

request.shresponse.json

# Active bushfires in NSW
$ curl -H "X-API-Key: $EMERGENCYAPI_KEY" \
    "https://emergencyapi.com/api/v1/incidents?state=nsw&eventType=bushfire"

# Is this postcode in a declared disaster area?
$ curl -H "X-API-Key: $EMERGENCYAPI_KEY" \
    "https://emergencyapi.com/api/v1/declarations/postcode/2480"

# Live river levels and flood classifications
$ curl -H "X-API-Key: $EMERGENCYAPI_KEY" \
    "https://emergencyapi.com/api/v1/gauges?state=qld"

# 200 OK  application/geo+json

{
  "type": "FeatureCollection",
  "features": [{
    "id": "nsw-rfs-1234567",
    "geometry": { "type": "Point", "coordinates": [150.604, -33.883] },
    "properties": {
      "title": "Bush Fire - Warragamba",
      "eventType": "bushfire",
      "warningLevel": "watch_and_act",
      "source": { "state": "nsw", "agency": "RFS" }
    }
  }]
}

Used by teams at

Who this is for

Built for developers, insurers, newsrooms and utilities who need this data to be right.

A developer desk with a laptop and phone showing a live incident map

Developers

Ship safety features without maintaining 34 feeds

Every state publishes its own data, in its own format, on its own schedule. We handle all of it so you do not have to. One endpoint, one schema, every jurisdiction.

Good for tracking apps, monitoring tools, smart home, field safety, anything that needs to know what is happening near a location.

See what developers build

An archival map room with a drawer open on a dated map sheet

The archive

Point in time, not a best guess after the fact

4.8 million archived incidents going back to 1840, each one timestamped as it was reported. Ask what was active on a date and get the answer that was true then, not a reconstruction.

Coverage is continuous from the 1930s, with a sparse tail of older events reaching back to 1840.

How the archive is structured

A property exposure map with a hazard zone crossing a local government boundary

Insurance and risk

See your exposure as it moves

Live peril data across every state, tied to location. Plus a timestamped historical record you can stand behind at claim time.

Insurance and risk

A newsroom wall of live map and feed panels

News and media

Power your live incident map from one source

Fires, floods, warnings and road closures nationwide, updating as they break. No scraping 8 different state websites during a bad week.

Newsroom use

Transmission towers and a substation inside a single monitored area

Utilities and infrastructure

Know what is happening near your network

Poles, lines, towers, substations, sites. Feed your asset locations in, get alerts when an incident lands nearby.

Works for anyone with assets in the field.

Utilities and infrastructure

Disaster declarations

Stop checking declared areas by hand

Telehealth platforms and providers currently answer “is this address in a declared area” by reading government notices and PDFs, one at a time, per patient. It is slow, it is manual, and it is out of date the moment an instrument is revoked. This turns it into a lookup.

Look it up at the point of care.: Pass a postcode, an LGA code or a lat/lng and get the current declared status for that area, with the instrument and the dates it covers. One call, in the workflow, instead of a tab open on a government PDF.
It changes without telling you.: Declarations are added, extended and withdrawn on the authority’s schedule, not yours. We track the published sources so a status checked this morning is the status that is actually current, not the one from the last time somebody remembered to look.
Every answer is dated and sourced.: Each response carries the AGRN, the instrument type and the source it came from, so the status you acted on can be shown later exactly as it stood at the time. The practitioner still records their own reasoning; this is the area fact underneath it.

EmergencyAPI reports the declaration and funding activation status of an area, as published by government sources. It does not provide medical, billing or legal advice, and it does not determine whether any exemption applies. That decision rests with the treating practitioner, who documents it and their clinical reasoning at the time of service.

How providers use it Read the guide

Built for integration

Every official source, one contract to write against

One schema, every jurisdiction

New South Wales calls it a category, Queensland calls it a warning level, South Australia publishes neither. Every record arrives in the same shape no matter who issued it.

NSW RFScategory: "Watch and Act"

QLD QFESwarningLevel: "WATCH_AND_ACT"

SA CFSstatus: "Going"

"warningLevel": "watch_and_act"

"eventType": "bushfire"

"source": { state, agency, feedId }

Attribution travels with the data

Every record carries the agency that issued it, the licence it is published under, and the moment we fetched it. You never have to reconstruct provenance.

agency: NSW RFS
licence: CC BY 4.0
fetched: 16:46:12 +10:00

Retractions are explicit

When an agency pulls an incident, you get a tombstone and a reason. Records do not quietly disappear between polls.

"Bush Fire - Warragamba"

retractedreason: upstream_removed

Built to be read by machines

GeoJSON and CAP-AU Atom out of the box, cursor pagination for backfills, and an OpenAPI spec you can generate a typed client from.

alerts.ts

schema.json

const res = await fetch(
  "https://emergencyapi.com/api/v1/incidents",
  { headers: { "X-API-Key": key } }
);

const { features } = await res.json();
// GeoJSON. Also available as CAP-AU Atom.

Built for enterprise integration

The questions a procurement team asks first, answered up front.

CAP-AU Validated: CAP Atom feed validates against the CAP-AU Profile v3.0 (OASIS CAP 1.2).
Official Government Feeds: Built on official Australian government feeds, with the few community-decoded sources clearly flagged.
Supply Nation Registered: Registered supplier on the Supply Nation platform.
Australian-Hosted Infrastructure: All data stored and processed in AWS Sydney, on SOC 2 Type II infrastructure (Vercel and Supabase).
Reliability: Self-healing infrastructure and per-feed monitoring. See our SLA.
Security: API-key auth, row level security, rate limiting, and a published self-assessment.

Full compliance details at /compliance.

Pull your first incident in about a minute

Create a key, call one endpoint, and every official source comes back in the same shape. The free tier covers 5,000 requests a month and never asks for a card.

Get an API key Read the docs

Disaster declarationsGET /v1/declarations

vicCentral-East Victorian StormsFlood, Storm
qldQuilpie Shire Rainfall and FloodingFlood
waSevere Storm across the South West and Great Southern in Western AustraliaStorm

River gaugesGET /v1/gauges

SA1.24 m · Below minorMingays (Kapunda) (Light River)
QLD-0.25 m · Below minorHawthorne AL
NSW1.48 m · Below minorJemalong Weir DS (Lachlan River)