Reference · built on requestCommons signalAir, water & environment

Hub'Eau

French water data APIs from Eaufrance: near-real-time hydrometry, groundwater levels, river temperature, and water-quality analyses.

Request accessPricing ↗

About

Hub'Eau is the API platform of the French water information system, Eaufrance, built by BRGM with the Office français de la biodiversité (OFB). It exposes national water databases as REST APIs: hydrometry from the PHyC platform run by the Service Central Vigicrues, groundwater levels from ADES, river temperature and physico-chemical quality from Naïades, plus drinking-water controls, abstraction volumes, and coastal monitoring. Responses come as JSON, GeoJSON, or CSV, with no registration.

Through Fibric, an operator watches the stations that matter to your sites or your supply routes and proposes a notice, a hold, or an evidence file for your approval, with the observation it read attached.

This is a reference listing. It documents what Fibric would read from Hub'Eau and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Hydrométrie v2: referentiel/sites and referentiel/stations, then observations_tr for water level H and discharge Q, refreshed from PHyC every 5 minutes
  • Hydrométrie obs_elab: daily and monthly mean discharge (QmnJ, QmM) and instantaneous daily and monthly extremes, updated daily
  • Piézométrie: stations, validated chroniques from ADES integrated daily, and chroniques_tr with raw hourly levels from telemetered piezometers
  • Température des cours d'eau: station and chronique from automatic sensors, synchronised with the Naïades database
  • Qualité des cours d'eau v2: station_pc, operation_pc, analyse_pc, and condition_environnementale_pc from Naïades, covering France and the overseas departments
  • Further APIs for drinking-water controls, water abstraction volumes, coastal monitoring, hydrobiology, fish surveys, and public water-service indicators

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Prepare a site for a rising river

    The operator polls observations_tr for H at the stations upstream of your site, watches the trend, and proposes the preparation notice for your approval, with the readings and their code_statut on the record.

    With Storm Prep, Severe Weather Notice

  • Prove abstraction stayed within the permit

    Groundwater levels from chroniques and abstraction volumes from the Prélèvements en eau API sit beside your own meter reads. The operator assembles the evidence file for the permit review and proposes it for sign-off.

    With Permit Check, Compliance Evidence

  • Hold inbound freight on a low river

    When Q at a station on a barge route falls, the operator flags the shipments routed through it and proposes a delay notice to the buyers concerned, citing the observation it read.

    With Inbound Delay, Lead-Time Drift

Requirements

  • The station or site codes you follow, for example code_entite for hydrometry or code_bss and bss_id for piezometers
  • Queries filtered by area, date, and parameter, which the terms ask of every client to spare the shared infrastructure
  • Paging by page or cursor with size, and a plan for the 20 000-record access depth on each query
  • A start date for observations_tr no more than one month back, expressed in UTC
Authentication
None. Hub'Eau APIs are open: you call them over HTTPS without registration or prior authorisation and cite the dataset's author under the Etalab Open Licence.

Limits

  • Real-time hydrometry keeps one month of history; older levels and flows come only as elaborated daily or monthly values
  • Access depth is capped at 20 000 records per query and URLs at 2 083 characters; split large pulls by station and date
  • The river-temperature network lists about 760 stations, of which only around fifty still report
  • No availability or performance guarantee; the terms exclude compensation for outages

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Hub'Eau ↗

Questions and answers

Does Hub'Eau need an API key?
No. The terms state you may access the open APIs without registration or prior authorisation. Data is published under the Etalab Open Licence; cite the dataset's author when you reuse it. The terms also ask you to filter queries and compress exchanges to limit load on the shared platform.
How current is the hydrometry data?
Real-time level and discharge observations are stored in PHyC every 5 to 60 minutes, and the API refreshes from PHyC every 5 minutes with one month of history. Elaborated daily and monthly values update daily. Validated groundwater levels arrive from ADES daily; telemetered piezometers report raw hourly readings.
What paging and size limits apply?
Each operation has a default and a maximum page size, up to 20 000 per page. The access depth, page number times page size, is capped at 20 000 records, and a URL at 2 083 characters. observations_tr pages with cursor rather than page.
Ask about Hub'Eau

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Eaufrance, operated by BRGM with OFB (hubeau.eaufrance.fr). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy