# NPS Park Alerts & Conditions (`scrupulous_waterbird_m4w/nps-park-alerts`) Actor Scrape current alerts, closures, and conditions for US National Park Service sites. Filter by state and category. No API key required. - **URL**: https://apify.com/scrupulous_waterbird_m4w/nps-park-alerts.md - **Developed by:** [Mori](https://apify.com/scrupulous_waterbird_m4w) (community) - **Categories:** Travel, Lead generation, Other - **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 ## NPS Park Alerts & Conditions Scrape current alerts, closures, and conditions for US National Park Service sites. Each record is enriched with the park name and state. Built on the public [NPS Data API](https://www.nps.gov/subjects/developer/api-documentation.htm) — no API key required. ### What it does - Pulls the live alerts feed (`/api/v1/alerts`) from `developer.nps.gov`. - Enriches each alert with park name, state, and homepage via `/api/v1/parks`. - Filters: US state(s), alert category, free-text search against title + description. - One unified JSON record per alert with stable schema. ### Input | Field | Type | Default | Description | |---|---|---|---| | `stateFilter` | string (CSV of 2-letter codes) | empty | e.g. `CA,AZ,UT`. Empty = all 50 states + DC + territories. | | `alertTypeFilter` | enum | `all` | `Caution`, `Danger`, `Information`, `Park Closure`, or `all`. | | `searchQuery` | string | empty | Free-text query against title + description (e.g. `wildfire`, `bear`, `road closure`). | | `maxRecords` | integer | 100 | Cap on alerts returned. Max 5000. | | `includeParkDetails` | boolean | true | Enrich each alert with park name + state (one extra `/parks` request per 10 unique parkCodes). | ### Output One record per alert: ```json { "id": "74D6113F-1B0B-4CB6-AEAF-E5BB6A6E2304", "parkCode": "grca", "parkName": "Grand Canyon National Park", "parkUrl": "https://www.nps.gov/grca/index.htm", "stateCode": "AZ", "title": "Stage 2 Fire Restrictions—VERY HIGH FIRE DANGER", "alertType": "Danger", "severity": "high", "description": "Stage 2 fire restrictions for South Rim, North Rim, and Inner Canyon are in effect…", "url": "https://www.nps.gov/grca/learn/management/fireinformation.htm", "lastIndexedDate": "2026-07-06 00:00:00.0", "scrapedAt": "2026-07-09T22:00:00.000Z" } ``` ### Severity mapping The NPS Data API exposes `category` (Caution / Danger / Information / Park Closure). This actor adds a derived `severity` field: | Category | Severity | |---|---| | Information | low | | Caution | medium | | Danger | high | | Park Closure | critical | ### Pricing Free tier: 1000 NPS API requests/hour (DEMO_KEY). Default run = 1 alerts request + 1 parks request per 10 unique parkCodes. A 100-record filtered run with no `includeParkDetails` false is well under the limit. ### Limitations - DEMO_KEY rate limit is 1000 requests/hour. High-volume users should register a free personal API key at `nps.gov/subjects/developer/get-started.htm`. - The NPS API does not expose historical alerts — only current state. - The alerts feed is updated nightly by NPS, not in real time. ### Changelog - 0.1.0 — initial release. # Actor input Schema ## `stateFilter` (type: `string`): Optional. Comma-separated list of 2-letter US state codes (e.g. 'CA,AZ,UT'). When set, only alerts for parks in those states are returned. Leave empty for all 50 states + DC + territories. ## `alertTypeFilter` (type: `string`): Optional. Restrict to one NPS alert category. ## `searchQuery` (type: `string`): Optional. Free-text query against the alerts index (matches title/description). Useful for 'wildfire', 'road closure', 'bear', etc. ## `maxRecords` (type: `integer`): Cap on total alerts returned. Default 100, max 5000. ## `includeParkDetails` (type: `boolean`): When true, each alert is enriched with park full name, state, and URL via the /parks endpoint (one extra request per unique parkCode). Default true. ## `proxyConfiguration` (type: `object`): Proxy settings. Free-tier apify runs usually don't need a proxy against developer.nps.gov. ## Actor input object example ```json { "stateFilter": "", "alertTypeFilter": "all", "searchQuery": "", "maxRecords": 100, "includeParkDetails": true, "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `id` (type: `string`): No description ## `parkCode` (type: `string`): No description ## `parkName` (type: `string`): No description ## `parkUrl` (type: `string`): No description ## `stateCode` (type: `string`): No description ## `title` (type: `string`): No description ## `alertType` (type: `string`): No description ## `severity` (type: `string`): No description ## `description` (type: `string`): No description ## `url` (type: `string`): No description ## `lastIndexedDate` (type: `string`): No description ## `scrapedAt` (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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("scrupulous_waterbird_m4w/nps-park-alerts").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("scrupulous_waterbird_m4w/nps-park-alerts").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 scrupulous_waterbird_m4w/nps-park-alerts --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrupulous_waterbird_m4w/nps-park-alerts" } } } ``` 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 ` 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/4gCbBPvgXWHFcFj4A/builds/6yOSZFpgyqCZmwuDE/openapi.json