A partner-facing REST API over the Flood Sentinel data store: station metadata, live readings, history and flood thresholds across 2,300+ live gauges and a 20,900+ station national archive — plus ML flood forecasts at the stations we model. JSON in, JSON out, BoM attribution included.
All data endpoints live under /bom/v1 and require a Bearer token (role api_customer or admin).
GET /bom/v1/stations — filter by state, type or bbox. GET /bom/v1/stations/{id} for detail and /parameters for what each gauge measures.
GET /bom/v1/stations/{id}/readings for time series, /latest for the most recent value per parameter.
Query readings?from=&to= for historical water level and rainfall — how far back you can go scales with your plan (7 days on Free → the full record on Atlas).
GET /bom/v1/routing/network returns the routing graph and /stations/{id}/upstream the tributary topology.
GET /bom/v1/forecast/{id} — ML-based flood forecast where the station is modelled, out to 72 hours at gated stations. GET /bom/v1/stations/{id}/validation returns the measured skill metrics for that station.
GET /bom/v1/stations/{id}/thresholds for the minor/moderate/major flood classifications, GET /bom/v1/alerts for active alerts.
GET /bom/v1/coverage — station totals and live counts by state and kind, with the freshness window we count as "live".
JWT auth: register, log in for an access token, then send it as Authorization: Bearer <token>.
Every authenticated response carries X-RateLimit-Plan, X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; unauthenticated responses carry none of them, because no key has been identified to budget against. Every response, authenticated or not, carries an attribution field and api_version. Errors return {"error", "status"} with the matching HTTP code.
Flood Sentinel provides decision-support forecasts. It is not an official warning service — always follow Bureau of Meteorology flood warnings and your state emergency service (SES) directions.