One integration, every dataset

Every endpoint lives under https://dataquoll.io/api/v1 and takes a bearer token. The free tier covers 5,000 requests a month and never asks for a card.

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.

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.

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.
• 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.

The OpenAPI spec drives this reference, the interactive playground and the Markdown edition for agents and LLMs. Version 1.50.0.