Connections
Connections attach data sources (LibreLinkUp, Dexcom Share, Medtronic CareLink, Tandem Source, Medtrum EasyFollow, Nightscout URLs, provider integrations) to a patient. Ingress from these connections is itself rate-limited (120/min bucket) to absorb Nightscout bursts.
Cloud polling: LibreLinkUp and Dexcom Share are stable (Dexcom fiel a xdripswift: Auth+LoginById, appId d89443d2…, hosts share2/shareous1/share.dexcom.jp). CareLink (OAuth CarePartner con webview, como xDrip/xukka: discovery → PKCE → patient/monitor/data → periodic → guardianM2M → legacyConnect), Tandem Source (SGV-only in v1) and Medtrum EasyView (fiel a xdripswift: easyview.medtrum.eu, AppTag, chart.sg, solo status C, caregiver multi-paciente) are experimental. Medtrum cloud can be gated with MEDTRUM_CLOUD_ENABLED=0 (uploader path keeps working). Eversense and Twiist are intentionally not offered (tiny EU footprint, no reusable bridge).
Public API (API key)
Credentials are never exposed: tokens and passwords are stripped from every response. All four endpoints require the key to be linked to the patient.
# List a patient's connections (paginated, max 100)curl "https://api.levelcast.org/api/v1/public/patients/PATIENT_ID/connections?page=1&limit=50" \ -H "X-API-KEY: lc_your_key_here"
# Single connectioncurl "https://api.levelcast.org/api/v1/public/connections/CONNECTION_ID" \ -H "X-API-KEY: lc_your_key_here"
# Rename (only name/enteredByName are writable via API)curl -X PUT "https://api.levelcast.org/api/v1/public/connections/CONNECTION_ID" \ -H "Content-Type: application/json" \ -H "X-API-KEY: lc_your_key_here" \ -d '{ "name": "Left arm sensor" }'
# Deletecurl -X DELETE "https://api.levelcast.org/api/v1/public/connections/CONNECTION_ID" \ -H "X-API-KEY: lc_your_key_here"Reads need the read scope; update/delete need write. Unknown or foreign IDs return 404 (no distinction, to avoid ID probing).
Dashboard
The dashboard manages connections with session auth (POST /api/v1/connections, provider pairing flows, LibreLinkUp import). Pairing new credentials is intentionally unavailable via API key — keys can only inspect, rename and delete.