REST API Reference

Public read endpoints are open and keyless. Responses are JSON with a 5-minute server-side cache. Write operations (branding sync, report submission) are documented per endpoint below.

Hatch data — hatch-chart/v1

Base URL: https://api.hatchchartapp.com/wp-json/hatch-chart/v1 — member org sites expose the same namespace at their own domain.

  • GET /hatches — full payload: all hatches, 12-month schedule, video/image source registry. Optional ?org=CODE filters to one organization’s assigned hatches.
  • GET /hatches/{slug} — single hatch by slug, e.g. /hatches/sulphurs

Each hatch includes: name, slug, surface / subsurface months, lifecycle stage images and hook sizes, fly patterns with tying recipes, entomology and tactics HTML, field notes, and machine-readable push notification trigger conditions.

Organizations & rivers

  • GET /chapter?code={CODE} — org branding, region, license status, social links. Never returns API keys.
  • GET /rivers?code={CODE} — river list with USGS gauge IDs, wading-safety thresholds, and access points.
  • GET /subscriber/orgs?token={SUB-TOKEN} — org configs unlocked by a subscriber token.
  • POST /organization/connect — org plugin handshake; requires org_code + api_key in the body.
  • POST /organization/sync — push branding from an org site to central; same credentials.

Org directory (namespace hatch-chart-license/v1): GET /orgs lists all active organizations; GET /orgs/{code} resolves an org code to its website URL — this is how the mobile app finds each org’s server.

Field reports & push

  • GET /reports?org={CODE} — approved hatch reports; optional river, limit, since params.
  • POST /reports — submit a report (rate-limited to 5 per IP per 24 hours).
  • POST /push/register / POST /push/unregister — device push token management with per-alert-type preferences.

Try it now: curl https://api.hatchchartapp.com/wp-json/hatch-chart/v1/hatches

Hatch Chart  ·  Conditions  ·  API Docs  ·  hatchchartapp.com

© 2026 Hatch Chart App  ·  info@hatchchartapp.com