Answers about any place in Australia.
DataQuoll turns fragmented Australian public data into one view of a location: what has happened there, what is happening now, and the conditions around it.
# What has happened at this location?
$ curl -X POST -H "Authorization: Bearer $DATAQUOLL_KEY" \
"https://dataquoll.io/api/v1/hazard-history/point" \
-d '{"lat": -28.8078, "lng": 153.2766}'
# What is happening near it right now?
$ curl -H "Authorization: Bearer $DATAQUOLL_KEY" \
"https://dataquoll.io/api/v1/incidents?state=nsw&eventType=bushfire"
# What are the river levels around it?
$ curl -H "Authorization: Bearer $DATAQUOLL_KEY" \
"https://dataquoll.io/api/v1/gauges?state=qld"# 200 OK application/json
{
"location": { "lgaName": "Lismore", "stateCode": "NSW" },
"declared": {
"distinctCount": 27,
"earliest": "2009-03-30",
"latest": "2025-03-03"
},
"observed": { "archiveTotal": 7, "earliest": "1988-04-07" },
"gauge": { "name": "Lismore (Wilsons River)", "distanceM": 404 }
}Used by teams at
A real answer
Send two coordinates and get back what is on record for that place.
This is output from the production API, measured on 2026-10-09. Its declared lane needs the Organisation licence. The coordinates are a street in Lismore, NSW, and the radius is 1 km.
curl -X POST https://dataquoll.io/api/v1/hazard-history/point \
-H "Authorization: Bearer $DATAQUOLL_KEY" \
-H "Content-Type: application/json" \
-d '{"lat": -28.8078061, "lng": 153.2766097, "radiusKm": 1}'{
"location": { "lgaName": "Lismore", "stateCode": "NSW" },
"declared": { "distinctCount": 27, "earliest": "2009-03-30" },
"observed": { "archiveTotal": 7, "earliest": "1988-04-07" },
"gauge": { "name": "Lismore (Wilsons River)", "distanceM": 404 },
"coverage": [ "... what the answer does not know" ]
}- 27
- declared disasters since 2009
- 1988
- earliest event recorded at this location
- 404 m
- to the Lismore (Wilsons River) gauge
The same event, published three times
DisasterAssist, the national recovery funding register and the state spatial service each publish these declarations separately, so 67 rows describe 27 events. You get the 27 events, and each one names the authorities that recorded it.
It also tells you what it misses
The February 2022 flood put this street under water, but the observed lane holds no record of it at this precision. It is here through the declared lane, as AGRN 1012. Every response carries its own limits: how precisely each record is located, which records have no date, and the fact that an absent record is not evidence that nothing happened.
Who this is for
Built for developers, insurers, newsrooms and utilities who need this data to be right.
Developers
Ship safety features without maintaining any feeds yourself
Every state publishes its own data, in its own format, on its own schedule. You read it through one endpoint, in one schema.
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
The archive
Point in time, not a best guess after the fact
4.5 million archived records going back to 1840, each with the date its source gave. Ask what was active on a date and get what was recorded, not a guess.
Coverage is continuous from the 1930s, with a sparse tail of older events reaching back to 1840.
How the archive is structured
Insurance and risk
See your exposure as it moves
Live peril data tied to location, plus a timestamped historical record you can stand behind at claim time.
Insurance and risk
News and media
Power your live incident map from one source
Fires, floods, warnings and road closures, updating as they break. No scraping state websites during a bad week.
Newsroom use
Utilities and infrastructure
Know what is happening near your network
Poles, lines, towers, substations, sites. Check each asset location against live incidents and see when one lands nearby.
Works for anyone with assets in the field.
Utilities and infrastructureWhat you can ask
Every question below is answerable today, with a key and one request.
- What has happened at this location?
- The observed record plus every declaration covering it, back through the archive.
- What is happening near it right now?
- Live incidents within a radius or a bounding box.
- Has this place been inside a declared disaster area?
- Declared status by local government area or postcode, counted once per event.
- Which incidents belong to the same event?
- The event they belong to, with a boundary drawn around its incidents and the suburbs it covers.
- What are the river levels around it?
- Live gauge readings, with the Bureau flood classification where one exists.
- What did this look like at a moment in the past?
- What was active at that moment, from what was recorded, not guessed after the fact.
One platform, three ways in
Developers reach the data through the API, and Intelligence puts the answer together. Monitor is the one we are still building.
For developers
DataQuoll API
Available now
Every dataset behind one integration, one schema and one key, instead of a scraper per agency.
- Live incidents, warnings, declarations and river gauges
- Every incident in the same shape, with the warning level each agency states, ready to filter on
- Ask for a radius or a box and get back only what is inside it
- Source attribution travelling with every record
For analysts and risk teams
DataQuoll Intelligence
Available now
It is the assembled answer rather than the raw record, and it covers what has happened at a location and what was true around it.
- Per-location hazard history: the observed record, plus the declared lane with the Organisation licence
- An archive of 4.5 million records, earliest 1840
- Point-in-time snapshots reconstructed from the archive
- Declared-area status by local government area, counted once per event
For teams with places to watch
DataQuoll Monitor
In development
Standing watches on the locations and assets that matter to you, so a public event reaches your systems when it becomes relevant to one of them. Not yet available.
- Mining sites, substations, network and telecommunications assets
- Property portfolios, depots, farms
- Today the API gives you everything needed to build this yourself
Built for integration
Every incident and warning, one contract to write against
One schema
Every incident and warning arrives in the same shape, whichever agency issued it.
Retractions are explicit
Ask for retracted incidents and each one stays visible for 24 hours, marked, with a reason.
Built to be read by machines
GeoJSON your mapping tools load directly, and a spec you can generate a typed client from.
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 and manual, and it is out of date the moment an instrument is revoked. DataQuoll turns that 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 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.
DataQuoll 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.
At home
Know when something happens near home.
This is already the most common thing people do with DataQuoll. Home Assistant users pull nearby incidents into their own dashboards and automations, and build whatever they want on top.
What people build
- A light that changes colour when there is a fire within ten kilometres
- A notification when a nearby river crosses a flood classification
- A dashboard card showing what is active in their own local government area
- A speaker announcement when a warning is raised near the house
The free tier covers personal use like this: up to 5,000 requests a month in total, of which at most 2,000 can go to endpoints other than /incidents/nearby, such as river gauges. The Home Assistant integration polls /incidents/nearby and uses most of the total at its 10-minute default, so anything else you poll comes out of what is left. DataQuoll supplies the data; the automation is yours.
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).
- Every Source Credited
- Every source is named and credited, and the few community-decoded ones are flagged.
- Supply Nation Registered
- Registered supplier on the Supply Nation platform.
- Hosting
- Your account record, API keys and usage data stay in Sydney. Vercel and Supabase hold SOC 2 Type II attestations.
- Reliability
- Published reliability targets and support response times. See our SLA.
- Security
- API-key auth, row level security, rate limiting, and a published self-assessment.
Full compliance details at /compliance.
Start with a question about a place
The free tier covers 2,000 requests a month for evaluation and non-commercial projects, and never asks for a card.
Watching sites or assets? See the utilities use case. Larger or non-standard needs? Talk to us.
- ntCentral Australia Severe Weather EventStorm, Thunderstorm
- vicVictoria Storms and FloodsFlood, Storm
- nswBlacktown Severe Storm WeatherStorm
- QLD1.18 m · Below minorTagigan Rd (Tinana Creek)
- NSW1.44 m · Below minorJemalong Weir DS (Lachlan River)
- SA1.25 m · Below minorRiver Torrens at Holbrooks Road