The LLIF Data API
102 endpoints. RESTful. Typed responses. OpenAPI spec. Consent-gated participant data with full audit trail. Built for health and longitudinal lifestyle data at scale.
API access requires approval as a program organizer or app developer. See access model below.
What the API covers
Create, read, update, and delete health and lifestyle events. 620+ taxonomy nodes covering health, wellness, fitness, nutrition, symptoms, medications, mental health, body metrics, and environmental responses.
Correlation analysis, trend detection, calendar pattern analysis, frequency distributions, and ML-based event predictions. Per-participant and aggregate anonymous outputs.
Food, drink, and supplement tracking. Barcode lookup, USDA database search, and AI-assisted food identification. Macro and micro-nutrient calculation. Meal grouping and recipe support.
25+ weather, air quality, and pollen metrics automatically enriched per event by location and timestamp. Temperature, humidity, barometric pressure, AQI, PM2.5, PM10, NO2, O3, tree/grass/weed pollen, mold spores.
Participant enrollment, profile management, consent records, permission scoping, data export, and deletion request handling.
Structured ingestion from Apple Health, Google Health Connect, Fitbit, Garmin, Oura, Whoop. Manual entry, voice input, barcode scan, and template-based quick entry.
Plan creation and scheduling. Target and goal configuration. Automated compliance verification. Reminder management. Conditional plan triggers.
Program creation, configuration, and participant management. Aggregate anonymous reporting for program organizers. Marketplace publishing and access control.
Real-time event notifications for consent changes, compliance updates, data export requests, and participant permission modifications. Configurable per partner integration.
Access model
The API is not publicly open. This is intentional.
LLIF infrastructure carries legal obligations to participants. We hold partner access to the same standard. Access requires three things:
Approval as a program organizer or app developer
Submit a brief description of your app or program, your intended use of participant data, and your organization. We review and respond within 5 business days.
Execution of the LLIF Data Partner Agreement
The Data Partner Agreement is the legal framework governing your access to participant data. It establishes your obligations to participants, data handling requirements, and the scope of permitted data use. Non-negotiable terms. Standard legal review typically takes 1–2 weeks.
Sandbox access for development
Once approved, you receive sandbox credentials for development and testing. Sandbox data is synthetic — no real participant data is accessible until production approval. Production access requires a completed integration review.
Auth & security
The API uses bearer token authentication. Tokens are scoped to your partner account and the specific participants who have granted your program access.
Every API call is logged against:
This audit trail is available to participants via their data dashboard and to LLIF for governance review.
Response format
All responses are JSON. Typed schemas for all event categories are defined in the OpenAPI specification.
Key conventions:
{"value": 72, "unit": "bpm"})Versioning
The current version is v1.0. The API is versioned in the URL path (/v3/ prefix on all endpoints, reflecting the underlying data service version).
Breaking changes are announced with a minimum 90-day deprecation window. Non-breaking additions (new endpoints, new optional fields) are added without version bumps.
The API changelog is published in the Releases section of the News page.
View API Changelogv1.1 roadmap
In DevelopmentRoadmap items are subject to change. Subscribe to release notifications via the News page.