Skip to main content

Authenticated Access

NH48, NH52WAV, and Long Trails API access

Build against NH48.info datasets with a signed-in account and a scoped API key. Full dataset access requires a monthly plan or approved nonprofit grant; PeakList Pro includes gated Long Trails API downloads.

Legacy public dataset URLs remain online during the migration window, but authenticated API keys are the supported path for remote apps.
Sign in Open console
Monthly access

Production API plan

$19.99/mo

For apps, dashboards, and recurring remote fetches that need stable NH48 and NH52WAV dataset access.

Contact support
Nonprofit access

Request a grant

Nonprofits, volunteer groups, educational projects, and public-interest tools can apply for access. Support can approve with a single-use grant link.

Sign in first so the grant can attach to your NH48.info account.

PeakList Pro

Long Trails API

PeakList Pro members can issue a route-scoped key for the Long Trails catalog and individual trail packs. That key cannot access NH48 or NH52WAV bulk datasets.

The public Long Trails map and viewer remain available without an API key.

Plan limits

Choose the smallest plan that matches the workload

Free

NH48 API Free

10,000 requests/mo

For prototypes, personal tools, and low-volume integrations.

60 requests/minute

Production

NH48 API Pro

250,000 requests/mo

For recurring app, dashboard, and analytics usage.

600 requests/minute

Scale

NH48 API Business

2,000,000 requests/mo

For commercial apps and higher-throughput data products.

3,000 requests/minute

Grant

NH48 API Nonprofit

250,000 requests/mo

For approved public-interest, volunteer, education, and nonprofit work.

600 requests/minute

PeakList Pro

Long Trails API

1,000 requests/mo

For authenticated Long Trails catalog and trail-pack downloads included with PeakList Pro.

30 requests/minute • Long Trails routes only

Nonprofit application

Sign in first

Dataset endpoints

Protected datasets
3
Legacy sunset
October 1, 2026
Support
[email protected]

Long Trails request flow

  1. Send your API key in the x-api-key header when requesting the catalog.
  2. Choose a catalog slug, then request that route's pack. The catalog never exposes the backing bucket or object key.
  3. For large packs, use HEAD, Range, If-Range, or If-None-Match for resumable and conditional transfers.
curl -H "x-api-key: nh48_live_yourpublicid_yoursecret" \
  https://nh48.info/api/v1/datasets/long-trails

curl -H "x-api-key: nh48_live_yourpublicid_yoursecret" \
  -H "Range: bytes=0-1048575" \
  https://nh48.info/api/v1/datasets/long-trails/appalachian-trail

401 means the credential is missing, malformed, invalid, or expired. 403 peaklist_pro_required means the key is authenticated but does not include Long Trails. Unknown or invalid slugs return 404.

Management endpoints

  • GET /api/v1/me/access-summary
  • POST /api/v1/me/nonprofit-application
  • POST /api/v1/me/keys
  • DELETE /api/v1/me/keys/current

Example request

curl -H "x-api-key: nh48_live_yourpublicid_yoursecret" https://nh48.info/api/v1/datasets/nh48

Migration notes