# NOAA Tides & Water Level Predictions API (`koalastuff/noaa-tides-water-level-monitor`) Actor

Retrieve bounded NOAA CO-OPS tide predictions and water-level observations by station, date, datum, and interval for maritime and coastal data workflows.

- **URL**: https://apify.com/koalastuff/noaa-tides-water-level-monitor.md
- **Developed by:** [Timo Schmidt](https://apify.com/koalastuff) (community)
- **Categories:** Developer tools, Automation, News
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 noaa tide/water-level records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## NOAA Tides & Water Level Data API

[Open the NOAA Tides & Water Level Data API in the Apify Store](https://apify.com/koalastuff/noaa-tides-water-level-monitor)

### Local preparation only

This candidate is locally implemented and fixture-tested. It remains unpublished until the separate external-sync/build/run/publication approval gate is cleared.

### Try this first

Retrieve high/low tide predictions for The Battery, New York:

```json
{"stations":["8518750"],"product":"predictions","date":"recent","interval":"hilo","datum":"MLLW","timeZone":"lst_ldt","units":"english","maxResults":20}
```

### Buyer intent

Retrieve station-specific tide predictions and water-level observations for maritime operations, coastal dashboards, port analytics, and repeatable data workflows. This is distinct from weather alerts: output is station/time-series water data, not warnings or forecasts.

```json
{"stations":["8518750"],"product":"predictions","date":"recent","interval":"hilo","datum":"MLLW","timeZone":"lst_ldt","units":"english","maxResults":20}
```

### Reliability and limits

- Official NOAA CO-OPS Data API only; JSON GET requests, no browser, proxy, login, CAPTCHA, or paid service.
- One bounded request per station, at most 10 stations and 500 output records per run.
- Three retries for transient HTTP failures, 30-second request timeout, deduplication, structured partial-record rejection, and at least 1,000 ms between station requests.
- NOAA documents product-specific date limits and throttling guidance; keep date ranges small and do not attach high-frequency schedules.

### Output

Each dataset item includes `station`, `product`, `timestamp`, `value`, `units`, `datum`, optional flags, the exact official request URL, retrieval time, and a non-affiliation disclaimer. No contact or other personal fields are requested.

### Source and rights gate

NOAA CO-OPS Data API: <https://api.tidesandcurrents.noaa.gov/api/prod/>. NOAA documents station-based observations and predictions, JSON output, product-specific limits, and throttling guidance. NOAA public-data guidance supports reuse unless specifically annotated otherwise; this Actor credits NOAA, disclaims affiliation, and does not present output as official navigation or safety guidance. External publication remains owner-gated.

### Pricing hypothesis

- Actor start: USD 0.00005
- Tide/water-level record: USD 0.001

This is an estimate copied from the current portfolio model, not a confirmed price or revenue result.

# Actor input Schema

## `stations` (type: `array`):

One to ten 7-character water-level station IDs.

## `product` (type: `string`):

Official CO-OPS product to retrieve.

## `date` (type: `string`):

Use today, recent, or latest when no historical dates are supplied.

## `beginDate` (type: `string`):

Optional YYYYMMDD or YYYYMMDD HH:mm. Use with endDate for a bounded historical range.

## `endDate` (type: `string`):

Optional YYYYMMDD or YYYYMMDD HH:mm. Use with beginDate for a bounded historical range.

## `interval` (type: `string`):

Predictions only: hilo, h, or a minute interval supported by NOAA.

## `datum` (type: `string`):

Reference datum required by water-level products and used for predictions.

## `units` (type: `string`):

Metric or English units as returned by NOAA.

## `timeZone` (type: `string`):

GMT, local standard time, or local daylight-adjusted time.

## `maxResults` (type: `integer`):

Hard output and billing limit across all requested stations.

## `requestDelayMs` (type: `integer`):

Delay between station requests to respect NOAA service guidance.

## Actor input object example

```json
{
  "product": "predictions",
  "date": "recent",
  "interval": "hilo",
  "datum": "MLLW",
  "units": "metric",
  "timeZone": "gmt",
  "maxResults": 50,
  "requestDelayMs": 1500
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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("koalastuff/noaa-tides-water-level-monitor").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("koalastuff/noaa-tides-water-level-monitor").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 koalastuff/noaa-tides-water-level-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,koalastuff/noaa-tides-water-level-monitor"
        }
    }
}

```

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/xbNPPxeu0gZAhCs92/builds/G60FkqY6FllCv2K2W/openapi.json