# CHMI Czech River Levels API

> Live water levels and flows for Czech river gauges from the Czech Hydrometeorological Institute

- Vendor: `chmiczechriverlevelsapi` · version 1.0 · category Weather · tags river levels api, water level api, flood api, hydrology api, czech rivers api, chmi api, discharge api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/chmiczechriverlevelsapi
- This document: https://apiclay.com/docs/chmiczechriverlevelsapi.md
- OpenAPI 3.1: https://apiclay.com/api/chmiczechriverlevelsapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `chmiczechriverlevelsapi`
- Updated: 2026-11-18

## About

## CHMI Czech River Levels API

Open data from the Czech Hydrometeorological Institute: every river gauging station with river name, coordinates and its flood-warning levels, and the last day of 10-minute water level (cm) and discharge (m3/s) readings for any station.

Data comes from **hydro.chmi.cz** (https://hydro.chmi.cz). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/stations` to find a station `objID` such as `0-203-1-001000`, then `/station?station_id=0-203-1-001000`.

### Routes

#### GET `/stations` - Stations
No parameters.

Returns: `data.data.header` (column names) and `values[]` rows: `objID`, station name, river, latitude, longitude, flood-level thresholds (SPA1-4) for level and flow (about 90 KB).

#### GET `/station` - Station readings
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| station_id | path | string | yes | `objID` from `/stations`. |

Returns: `objList[0].tsList[]` per series (`tsConID` `H` level, `Q` flow) with `unit` and `tsData[]` (`dt`, `value`).

### Caveats

- Field names are Czech; readings are provisional operational data.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by hydro.chmi.cz.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /stations — Stations
- Gateway: `GET https://api.apiclay.com/v1/api/chmiczechriverlevelsapi/stations`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /station — Station readings
- Gateway: `GET https://api.apiclay.com/v1/api/chmiczechriverlevelsapi/station`
- Public query params: `station_id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/chmiczechriverlevelsapi/stations" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
