API reference
Hazard history
What official sources recorded near a location, unioned with the disaster declarations covering its local government area. Base URL https://dataquoll.io/api/v1.
/hazard-history/pointObserved record and declared status for an exact point
What official sources recorded near a location, unioned with the disaster declarations that covered its local government area. Two lanes are returned because both are required: the observed lane (historical archive plus live-era incident history within a radius) and the declared lane (declarations for the covering ABS LGA, counted once per AGRN even when several authorities recorded the same event). Measured example: a Lismore address returns the February 2022 flood only through the declared lane, because the spatial lane holds no record for it at address precision. POST with a JSON body is used deliberately so coordinates never appear in URLs or request logs; the request is read-only and safe to retry. Coordinates are never stored, logged, or echoed back, and the response is Cache-Control: no-store. This reports a RECORD and a declared STATUS. It is not an assessment of risk, insurability, or any obligation, and absence of a record is not evidence that nothing happened. Precision is reported per record: a record at postcode precision sits at a postcode centroid, which can be kilometres from the event.
Responses
| Status | Description |
|---|---|
200 | The observed record and declared status for the point. A point outside every Australian LGA returns a null location and an empty declared lane. This response uses one hazard history lookup. |
400 | Invalid body, lat, lng, radiusKm, or records. Error detail never repeats submitted values. |
401 | Missing or invalid API key |
403 | The account has used its hazard history lookups for the month (100 free, then blocks of 1,000) |
429 | Rate limit exceeded |
curl "https://dataquoll.io/api/v1/hazard-history/point" \ -H "Authorization: Bearer YOUR_API_KEY"