data api · England

EA Flood Monitoring API

Public flood warnings, river levels, rainfall and monitoring-station observations.

Claim this listing

Represent EA Flood Monitoring API? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified: flood warnings and flood alerts · flood areas · water level and flow measurements · monitoring station information · rainfall
Coverage llm-inferred: England
Resolution docs-verified: Water levels and flows usually sampled every 15 minutes (temporal); spatial resolution not stated
Update frequency docs-verified: Readings usually every 15 minutes; data transferred to the Environment Agency typically once or twice per day, more often during heightened flood risk
Formats docs-verified: JSON · RDF/XML · Turtle · CSV · HTML (browser view)
Access docs-verified: Free open data; no authentication or registration; Open Government Licence (version 3 per licence URL in docs); attribution statement requested

Useful for

Use cases llm-inferred: Nearest river-level and flow gauge lookup for FRA baseline flow context · Historic level and flow readings via startdate/enddate for hydrological model calibration · Flood warning and flood area screening within a radius of a site (lat/long/dist filter) · Latest rainfall and level readings as a context check for drainage strategy studies
Audience llm-inferred: flood consultants · hydrologists · drainage engineers · GIS analysts · civils engineers

Limitations

Constraints docs-verified: Labelled a trial/beta service; feedback requested · No service-level guarantee; should not be relied on for safety-critical applications · Does not replace the Agency's official channels for notifying the public of floods · Responses may be redirected at high load or in future versions; clients must follow standard HTTP redirects · Responses may be cached briefly; custom filtering reduces cache hits · Readings are sometimes updated in batches, so a complete history needs the since filter · Some endpoints impose a length limit by default; check the metadata limit and offset values · No rate limit documented; the docs recommend one call every 15 minutes (data/readings?latest) rather than crawling every station

Licence: Open Government Licence 3.0
Authentication: No authentication
GitHub stars: Unknown
Last commit: Unknown
Last successful page check: 14/10/2026
Page health: page reachable
Package: Not recorded
Verification: Not independently verified

Provenance & evidence

Public page checked: HTTP 200. Licence/auth left null where not established.

Metadata observed 14/10/2026 · editorial seed