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" }
    }
  }]
}

Trusted by teams at

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
waSevere Storm across the South West and Great Southern in Western AustraliaStorm
nswMid-Coast BushfiresBushfire

River gaugesGET /v1/gauges

NSW1.90 m · Below minorJemalong Weir DS (Lachlan River)
VIC3.22 m · Below minorShepparton (Goulburn River)
QLD1.02 m · Below minorThe Boulders (Babinda Creek)