Open data

Open data and API

Public, read only, CC BY 4.0.

CryoHealth is API driven end to end. Everything the app uses is available through the same documented endpoints below, so any partner or ministry can integrate without a negotiation, a contract or a fee. Endpoints are read-only and require no authentication.

curl https://cryohealth.io/api/public/lakes

Endpoints

• GET /api/public/lakes

  All monitored glacial lakes with current risk tier, location, and last update time.

  {
    "lakes": [
      {
        "id": "lk_shishper",
        "name": "Shishper glacial lake",
        "lat": 36.32,
        "lng": 74.65,
        "current_tier": "WATCH",
        "stale": false,
        "district_id": "hunza",
        "elevation_m": 3100,
        "last_updated": "2026-08-09T04:12:00Z"
      }
    ]
  }

• GET /api/public/lakes/{lakeId}

  A single lake's detail: current state, risk score history, alerts issued for it, and nearby glaciers.

  {
    "lake": { "id": "lk_shishper", "name": "Shishper glacial lake", "current_tier": "WATCH" },
    "history": [{ "score": 62, "tier": "WATCH", "confidence": 0.81, "observed_at": "2026-08-08" }],
    "alerts": [{ "id": "al_204", "title": "Watch: Shishper", "tier": "WATCH" }],
    "glaciers": [ ]
  }

• GET /api/public/hot-lakes

  Lakes currently at HIGH or CRITICAL tier only, ordered by risk score.

  { "lakes": [{ "id": "lk_shishper", "name": "Shishper glacial lake", "current_tier": "HIGH", "current_risk_score": 78, "downstream_population": 4200, "last_updated": "2026-08-09T04:12:00Z" }] }

• GET /api/public/alerts

  Every alert issued, newest first: dispatch tier, message text, target lake or district, and estimated impact window.

  {
    "alerts": [
      {
        "id": "al_204",
        "title": "Watch: Shishper glacial lake",
        "tier": "WATCH",
        "body_en": "Risk rising. Avoid contaminated water sources downstream.",
        "body_ur": null,
        "estimated_window": "next 24h",
        "affected_population": 4200,
        "created_at": "2026-08-09T04:12:00Z",
        "lake_name": "Shishper glacial lake",
        "district_name": "Hunza"
      }
    ]
  }

• GET /api/public/glaciers

  Glacier inventory (RGI v7 / GLIMS derived): area, length, elevation range, and observed status per glacier.

  { "glaciers": [{ "id": "gl_101", "name": "Shishper Glacier", "rgi_id": "RGI60-14.07524", "district_id": "hunza", "area_km2": 15.4, "status": "surging" }] }

• GET /api/public/glaciers/{glacierId}

  A single glacier's detail: observation time series, associated lakes, and recent disaster-related cases in its district.

  { "glacier": { "id": "gl_101", "name": "Shishper Glacier" }, "observations": [ ], "lakes": [ ], "cases": [ ] }

• GET /api/public/facilities

  Health facilities with a mapped location, type, and vulnerability rating, used to show downstream exposure.

  { "facilities": [{ "id": "fac_12", "name": "Gilgit District Hospital", "lat": 35.92, "lng": 74.31, "type": "hospital", "vulnerability": "medium" }] }

• GET /api/public/districts

  Reference list of districts and their province, used to filter every other endpoint.

  { "districts": [{ "id": "hunza", "name": "Hunza", "province": "Gilgit-Baltistan" }] }

• GET /api/public/protocols

  The prevention and care protocols the offline app draws on, with disaster-related protocols flagged.

  { "protocols": [{ "id": "pr_5", "title": "Safe drinking water after a flood", "is_disaster": true }] }

• GET /api/public/kpis

  Platform-wide indicators: lakes at HIGH or CRITICAL, alerts in the last 30 days, cases in the last 7 days, active community health workers.

  { "highLakes": 2, "alerts30d": 14, "cases7d": 9, "chws": 11 }

Update frequency

Lake risk tiers and glacier observations refresh within 4 hours of new Sentinel or MODIS imagery. Alerts and KPIs are generated in real time as events occur. Reference tables (districts, facilities, protocols) change only when the underlying dataset is updated.

Licence

Code is released under the MIT licence. Data returned by these endpoints is released under CC BY 4.0. Suggested attribution: “Data from CryoHealth (cryohealth.io), uExel Solutions, CC BY 4.0.”

Interoperability

CryoHealth does not currently claim conformance with HL7 FHIR or DHIS2. Because the platform is API driven and holds no personally identifiable data, adding those adapters is an integration task rather than a rebuild, and we intend to pursue both as national health system adoption requires it.

Public endpoints are rate limited. For higher volume access, contact us. It is free.