# NOAA Tides Scraper: High & Low Tide Predictions (`naimurhasanrwd/noaa-tides-scraper`) Actor

Pull high and low tide predictions for any US coastal station from the NOAA Tides and Currents public API. No login, no proxy, no browser.

- **URL**: https://apify.com/naimurhasanrwd/noaa-tides-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

## NOAA Tides Scraper

Pulls high and low tide predictions for any US coastal station from NOAA's
Tides and Currents public API. No login, no proxy, no browser.

### Input

| Field | Type | Notes |
|---|---|---|
| `stationId` | string | Required. NOAA CO-OPS station id, e.g. `8454000`. Default `8454000` (Providence, RI). |
| `days` | integer | Days of predictions to fetch, starting today. Default `2`. |
| `units` | string | `english` (feet) | `metric` (metres). Default `english`. |

### Output

One row per tide turn: `stationId`, `time` (station local time),
`tide` (`high` or `low`), `level`, `unit`.

### Notes

- Predictions are relative to the MLLW datum, the standard chart datum for US
  tide tables, so levels are comparable to printed tide charts.
- Times come back in the station's own local time including daylight saving,
  not UTC — a tide table is only useful in local time.
- NOAA reports a bad station id as HTTP 200 with an `error` object in the body
  rather than an error status, so that case is checked explicitly instead of
  being read as an empty result.
- `level` arrives as a string upstream and is converted to a number here, so
  the dataset sorts and charts numerically.

# Actor input Schema

## `stationId` (type: `string`):

NOAA CO-OPS station id, e.g. 8454000 (Providence, RI) or 9414290 (San Francisco, CA)

## `days` (type: `integer`):

How many days of predictions to fetch, starting today

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

english reports feet, metric reports metres

## Actor input object example

```json
{
  "stationId": "8454000",
  "days": 2,
  "units": "english"
}
```

# Actor output Schema

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

Every high and low tide the run predicted.

# 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 = {
    "stationId": "8454000"
};

// Run the Actor and wait for it to finish
const run = await client.actor("naimurhasanrwd/noaa-tides-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 = { "stationId": "8454000" }

# Run the Actor and wait for it to finish
run = client.actor("naimurhasanrwd/noaa-tides-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 '{
  "stationId": "8454000"
}' |
apify call naimurhasanrwd/noaa-tides-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,naimurhasanrwd/noaa-tides-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/qyhuLnqLeGGZPim9I/builds/2kw5xuNUU4n3JqGsy/openapi.json