Documentation

Example API

OGT adapters submit normalized payloads; OGT validates, maps to OGIS, and emits canonical events. Exact HTTP surfaces vary by runtime deployment—this illustrates the logical ingest shape.

Adapter payload (pre-canonical)

{
  "source_id": "abbott.librelinkup",
  "subject_id": "local:app:user-abc",
  "payload": {
    "record_id": "graph-12345",
    "subject_id": "local:app:user-abc",
    "timestamp": "2026-03-29T14:32:00.000Z",
    "value_mgdl": 142,
    "unit": "mg/dL",
    "trend_arrow": 4
  }
}

Canonical output (OGIS)

After adapter mapping and validation, consumers receive a glucose.reading event as documented in Example JSON. OGT may attach trace identifiers and received_at on envelopes—see Open Glucose Telemetry documentation.