Documentation
One integration, every dataset
DataQuoll is a data platform. It aggregates Australian public data that agencies publish fragmented, in formats never designed for software, normalises it into one schema, and turns it into a single view of a location: what has happened there, what is happening now, and the conditions around it. These docs cover authentication, rate limits, pagination, errors and every endpoint. For emergency incidents and warnings, 39 official feeds, 4 community-decoded SA pager feeds and 1 agency feed (NT PFES, licence not published) are polled today.
Your first request
Every endpoint lives under https://dataquoll.io/api/v1 and takes a bearer token. The free tier covers 2,000 requests a month for evaluation and non-commercial projects, and never asks for a card. An agent with no key can pay per request instead.
curl "https://dataquoll.io/api/v1/incidents?state=nsw&limit=5" \ -H "Authorization: Bearer YOUR_API_KEY"
Responses are GeoJSON by default, so they drop straight into Leaflet, Mapbox or MapLibre without transformation. CSV and CAP-AU are available on the endpoints that support them, on the Developer plan and above. The quickstart walks the whole thing end to end in about a minute.
Start here
Four things account for almost every integration question. Read them once and the rest of the reference is self-explanatory.
- AuthenticationCreating keys, sending them, and restricting a key to your own origins.
- Rate limitsWhat each tier allows, what a 429 looks like, and how to back off correctly.
- PaginationCursors, page sizes, and why offsets are the wrong tool for a live feed.
- ErrorsOne machine-readable error shape across every endpoint.
Endpoint reference
Generated from the OpenAPI spec, so it cannot drift from what the API actually does.
- Incidents5 endpointsLive and historical emergency incidents from every state and territory, in one GeoJSON schema.
- Events2 endpointsNearby incidents clustered into a single event with a boundary polygon and affected suburbs.
- Disaster declarations4 endpointsWhich local government areas sit inside a declared disaster area, by postcode, point or AGRN.
- River gauges4 endpointsWater level readings and BoM flood classifications from state water monitoring networks.
- Emergency facilities1 endpointWhere responders come from: police, ambulance, fire and SES facility locations nationally, searchable by radius.
- Mobile network sites1 endpointWhere the mobile networks' radio sites are: Telstra, Optus and TPG site records from the ACCC, searchable by radius, state, LGA or operator.
- Addresses1 endpointEvery Australian address from G-NAF, matched exactly from one line, with what is known about its point in the same answer.
- Publications3 endpointsOfficial documents from the publisher registry: police media releases first, versioned and kept after the publisher deletes them.
- States1 endpointPer-jurisdiction coverage: which agencies we carry and how fresh each one is.
- Status and metadata3 endpointsService health, the enum vocabulary, and the attribution every source requires.
- Hazard history1 endpointWhat official sources recorded near a location, unioned with the disaster declarations covering its local government area.
- Calendars3 endpointsIndustry calendars per jurisdiction: RDOs, public holidays, school holidays and shutdowns, verified against official lists, and whether a date is a working day.
Machine readable
The OpenAPI spec drives this reference, the interactive playground and the Markdown edition for agents and LLMs. Version 1.114.1.