National Park Service API
planned Executive · Tier 3 · API · Department of the Interior (NPS)
Official site (opens in a new tab) · All sources
What this source is
The NPS developer API (developer.nps.gov) exposes news releases, alerts, events, and multimedia (galleries, videos, webcams) across the park system as structured JSON. News and alerts are the current-flow value; multimedia is largely evergreen reference.
Identity and registry record
- Registry id
nps-api- Agency / parent organization
- Department of the Interior (NPS)
- Branch
- executive
- Type
- API
- Status
- planned
- Tier
- 3
- URL (home)
- https://www.nps.gov/subjects/developer/api-documentation.htm (opens in a new tab)
- Registered
- 2026-07-28
- Registry notes
- Search-corroborated 2026-07-28 (docs page is JS-shelled to research fetchers; read via our client at probe). Text endpoints first; multimedia opportunistic.
How we ingest it
- Channel
- API
- Method
- Would query news/alerts endpoints with a registered key (documented 1,000 req/hour).
- Request budget
- the agency class: at most 1,500 requests per day shared across every agency web source, counted from the fetch log (failed requests count too)
- Politeness
- robots.txt is honored as observed — including each host's crawl-delay, exactly — and every request identifies itself as fapd/0.1 (Free Agentic Publication Digester; +https://fapd.info/bot.html; contact: hustleyourcity@gmail.com); a refusal is recorded, never evaded
- Capture and hash
- captured raw content is hashed (SHA-256) into the day's committed provenance manifest, hash-chained day to day (PROVENANCE.md)
Ingestion health
Not ingested: the registry status of this source is planned.
Ingestion statistics
These figures describe this project's ingestion of this source — items we recorded and requests we made — and nothing else. They are not a measurement of the publisher.
Not ingested: the registry status of this source is planned. Ingestion statistics are measured for active sources only.
All time
No requests to www.nps.gov are recorded in the request log.
Last 30 days, day by day
No requests and no items were recorded in the last 30 days, so there is nothing to chart.