Authenticated Access
NH48 and NH52WAV API access
Bulk cloud fetches for the NH48 and NH52WAV datasets now live behind authenticated API keys. Use this surface to sign in with your shared NH48 account, review plan limits, issue a key, and switch your apps off the old public JSON downloads.
Legacy public dataset URLs remain online during the migration window, but they now carry deprecation headers and are being removed from public site navigation.
What changed
Protected datasets
2
Legacy sunset
October 1, 2026
Auth model
Shared NH48 login
Dataset endpoints
The authenticated dataset endpoints keep the same payload shape as the old bulk JSON files, but require an API key in the x-api-key header.
/api/v1/datasets/nh48/api/v1/datasets/nh52wav
Management endpoints
Your browser session is only used for key and usage management.
GET /api/v1/me/access-summaryPOST /api/v1/me/keysDELETE /api/v1/me/keys/current
Quick start
- Sign in with the same account you already use on NH48.app.
- Open the console and issue a key. The cleartext key is shown once.
- Switch your remote callers from
/data/nh48.jsonor/data/NH52WAV.jsonto the new dataset endpoints.
Example request
curl -H "x-api-key: nh48_live_yourpublicid_yoursecret" https://nh48.info/api/v1/datasets/nh48
Use cloud fetches from your app or backend. The goal of this migration is to stop relying on downloadable public bulk files.
Migration notes
- Legacy
/data/nh48.jsonand/data/NH52WAV.jsonare still available during phase 1, but they now emit deprecation and sunset headers. - First-party browse pages are being moved off full bulk JSON before the hard cutover phase retires those public URLs.
- Trail, plant, and long-distance route datasets are still public in this phase.
This deployment does not have Supabase client settings yet, so sign-in and console actions will stay disabled until the worker secrets are added.