← AI resource directorypublic-data-apis

public-data-apis · prepared

National Park Service API boundary

Official-source access, authentication, request-shaping, paging, freshness, legal, and interpretation boundaries for National Park Service API.

version 1.0.1freshness currentobserved 2026-09-25T02:08:03.379Z

resource.public-data.national-park-service-api
sha256:1b18c1331b031a7c98206665dcfa4792fe91f9e142e50e38e2579d1823608c82

Open canonical machine JSON →

Evidence-backed facts

  1. The documented NPS API exposes JSON endpoints for parks, alerts, articles, campgrounds, events, visitor centers, people, places, and related resources. This documentation review does not verify live records or complete park coverage. informative
  2. The Swagger contract declares api_key as a query API-key security scheme and requires it for GET /parks. No key was requested or used; authentication documentation is not authority to write records, reserve visits, or issue permits. Keep credentials out of public URLs and logs. informative
  3. For GET /parks, the documented parameters are parkCode, stateCode, limit, start, q, and sort; limit defaults to 50 and start defaults to 0. Its response schema exposes total, limit, start, and data. Do not assume a fields selector or these same parameters on other endpoints; no paging behavior was tested against live records. informative
  4. Park image metadata includes credit and URL; gallery-asset metadata separately includes constraintsInfo and copyright. A metadata URL, credit, or schema example does not independently grant reuse permission or verify asset availability. Current park notices, safety conditions, permissions, and media-specific rights require separate checks. informative