# UK Flood Monitoring Scraper: River Stations (`naimurhasanrwd/ukea-flood-scraper`) Actor

Pull UK river and flood monitoring stations via the Environment Agency open API: river, catchment, town and coordinates. No login, no proxy, no browser.

- **URL**: https://apify.com/naimurhasanrwd/ukea-flood-scraper.md
- **Developed by:** [Naimur Hasan](https://apify.com/naimurhasanrwd) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## UK Flood Monitoring Scraper

Pulls UK river and flood monitoring stations through the Environment Agency's
open API. No login, no proxy, no browser.

### Input

| Field | Type | Notes |
|---|---|---|
| `riverName` | string | Exact river name, e.g. `River Severn`. Omit for all. |
| `town` | string | Exact town name. Omit for all. |
| `maxItems` | integer | Cap on stations returned. Default `50`. |

### Output

One row per station: `stationId`, `label`, `riverName`, `town`,
`catchmentName`, `latitude`, `longitude`, `status`, `isActive`,
`dateOpened`, `measureCount`, `stationUrl`.

### Notes

- **`_limit` bounds source rows, not stations.** A station with several
  measures consumes several underlying rows, so `_limit=200` returns about 149
  stations. This Actor therefore over-requests and trims to `maxItems`, which
  is why you reliably get the number you asked for.
- The API is RDF-backed, so **single-valued fields sometimes arrive as
  arrays** — a station with two recorded names returns `label` as a list. The
  first entry is taken rather than letting an array land in a text column.
- `status` is a URI (`.../def/core/statusActive`); only its last segment is
  meaningful, and `isActive` is derived from it.
- Filters are exact matches, not substrings: `River Severn` works, `Severn`
  returns nothing.

# Actor input Schema

## `riverName` (type: `string`):

Exact river name, e.g. River Severn. Leave unset for all rivers.

## `town` (type: `string`):

Exact town name. Leave unset for all towns.

## `maxItems` (type: `integer`):

Cap on stations returned

## Actor input object example

```json
{
  "maxItems": 50
}
```

# Actor output Schema

## `items` (type: `string`):

Every monitoring station the run returned.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("naimurhasanrwd/ukea-flood-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("naimurhasanrwd/ukea-flood-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call naimurhasanrwd/ukea-flood-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,naimurhasanrwd/ukea-flood-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/f9ikqcNDcdjTtjhfs/builds/S3YZlgEPpRz7jpHJN/openapi.json