Welcome to InsideTracker

InsideTracker helps you turn health data from your Users into personalized insights they can understand and act on. Your application can create linked InsideTracker customer records, add or connect health data, retrieve outputs such as Inner Age and Recommendations, and present those outputs in your own product.

Use these guides for workflow context, implementation choices, and User-facing behavior. Use the API Reference when you need exact endpoint paths, request schemas, response schemas, examples, and status codes.

Add User data

Create linked customer records, add profile context, submit or process blood results, order lab tests, and connect supported wearable data.

Use health intelligence

Retrieve outputs such as Inner Age, Category Scores, Recommendations, Action Plan, and ProTips.

Enrich biomarker experiences

Use biomarker reference data, Optimal Zones, supporting research, and marker relationships to explain User data.

Operate your integration

Manage authentication, customer-level tokens, webhooks, sandbox testing, and asynchronous updates.

What You Can Build

InsideTracker integrations combine three layers: getting User data into InsideTracker, retrieving health intelligence, and operating the integration reliably.

Area	What it covers
Start Here	Authentication, linked customer creation, token storage, and the first working integration path.
Add User Data	Profile data, structured blood result submission, document-based blood result upload, Lab Connect, and supported wearable data.
Use Health Intelligence	User-facing outputs such as Inner Age, Category Scores, Recommendations, Action Plan, and ProTips.
Enrich Experiences	Biomarker reference data, Optimal Zones, supported biomarkers, supporting research, and physiomarker context.
Operate and Test	Customer account maintenance, webhooks, sandbox testing, async status handling, and integration operations.

The data you add or connect determines which outputs are available for each User. The Add User Data guides explain the input layer. The Use Health Intelligence guides explain the outputs and engagement workflows those inputs can support.

Integration Model

InsideTracker integrations follow this model:

Authenticate your backend with InsideTracker.
Create a linked InsideTracker customer record for your User.
Store the identifiers and credentials that connect your User record to the InsideTracker customer record.
Add or connect the User's health data.
Retrieve the outputs available for that User.
Use webhooks and status endpoints to handle asynchronous processing, output availability, and operational updates.

The model stays stable across implementations. Your main choices are which data sources your Users provide and which outputs your product shows. Structured blood result submission, document-based blood result processing, Lab Connect, Fitbit, and Apple HealthKit are data onboarding options inside the same model.

Core Concepts

Concept	Description
Partner	The organization integrating InsideTracker into its product or service.
User	The individual in your product or service whose health data is personalized through InsideTracker.
`extId`	The external User identifier used to map your User record to the corresponding InsideTracker customer record.
Service-level token	Token used by your backend for Partner-level operations such as creating linked customer records or managing organization resources.
Customer-level token	Token used for User-specific operations, such as adding profile data or retrieving User outputs.
User data onboarding	The workflows that get User data into InsideTracker, including profile data, blood results, lab tests, and supported wearable data.
Health intelligence output	An InsideTracker result or workflow generated from User data, such as Inner Age, Category Scores, Recommendations, Action Plan, or ProTips.
Enrichment data	Supporting data used to explain health information, such as biomarker references, ranges, units, research, and marker relationships.

Where To Start

If you are new to InsideTracker, start with Getting Started. It walks through a small end-to-end path:

Authenticate.
Create a linked customer record.
Store customer-level credentials.
Add profile data.
Add a structured blood result.
Retrieve a personalized biomarker output.

After that, move to the guide that matches what you are building.

If you are building...	Read next
Your first API integration	Getting Started
Token handling and security	Authorization and Security
Linked customer creation and identifier mapping	Creating Users
Account maintenance after User creation	Customer Account Management
Profile and onboarding data collection	Adding Profile Data
Structured marker-value blood result submission	Add Blood Result
Document-based blood result processing	Blood Result Upload and OCR Blood Result Upload
Quest or Mobile Blood Draw lab ordering	Lab Connect
Fitbit or Apple HealthKit data workflows	Connecting Wearable Devices
Recommendations, adherence workflows, and timely insights	Recommendations, Action Plan, and ProTips
Async event handling	Webhooks

Guides And API Reference

The Developer Portal has two parts that work together:

Space	Use it for
Guides	Workflow context, prerequisites, implementation decisions, availability, and User-facing behavior.
API Reference	Exact endpoints, parameters, request bodies, response bodies, status codes, and examples.

When the guides and API Reference differ in level of detail, use the API Reference as the endpoint-level source of truth and the guides as workflow guidance.

Documentation Philosophy

Good documentation should help you build. These guides are here to explain what InsideTracker does, how the product behaves, and how to incorporate InsideTracker capabilities into the experience you are creating.

If anything is confusing, incomplete, or incorrect, let us know through your Partner support channel. Documentation should make implementation easier, and your feedback helps us keep improving it.

Implementation Expectations

InsideTracker integrations handle sensitive health information. Build with privacy, consent, and User trust in mind from the beginning.

Baseline expectations

Use sandbox environments before production.
Store service-level and customer-level tokens securely.
Keep User identifiers and extId mappings stable.
Use customer-level tokens for User-specific workflows.
Validate data before submitting it.
Handle asynchronous processing with webhooks, status endpoints, or both.
Design User experiences for pending, missing, insufficient, and unavailable data states.
Use the API Reference for current request and response schemas.

Need Help?

If something does not appear to work as documented, or if you need implementation guidance, contact the InsideTracker team through your Partner support channel.

When reporting an issue, include the environment, endpoint, request timestamp, relevant User identifier or extId, and any non-sensitive error details.