Glossary
Shared terminology for InsideTracker integration guides.
Glossary
This glossary defines shared product and implementation terms used across the InsideTracker documentation.
Public guides use Partner for the organization integrating with InsideTracker and User for the person whose health data is being processed. API paths, token names, and response fields may still use customer when they refer to the linked InsideTracker customer record for that User.
When an endpoint requires an exact field name such as extId, testId, resultId, or processId, the guide preserves the API field name.
People, Records, And Access
| Term | Meaning |
|---|---|
| Partner | The organization integrating with InsideTracker. In a B2B integration, you own the User relationship in your product or service. |
| User | The person whose health data is created, connected, submitted, analyzed, or displayed through your integration. |
customer | In API paths, auth scopes, token names, and source-system terminology, customer usually means the linked InsideTracker customer record for a User. |
| Linked InsideTracker customer record | The InsideTracker-side record created for your User. User-specific data, credentials, and outputs are attached to this record. |
extId | The durable identifier used to map your User record to the linked InsideTracker customer record. Provide and store a stable extId when possible. |
| Customer credentials | The customer-level access and refresh tokens returned for a linked InsideTracker customer record. Store them securely for User-specific API calls. |
| Service-level token | A bearer token used when your backend acts as your organization, such as creating Users, managing inventory, or recovering customer tokens. |
| Customer-level token | A bearer token used when your backend acts for one linked InsideTracker customer record, such as adding User data or retrieving User-specific outputs. |
| Webhook endpoint | Your configured HTTPS endpoint that receives InsideTracker event notifications. |
User Data And Reference Data
| Term | Meaning |
|---|---|
| Biomarker | A blood marker represented in InsideTracker biomarker reference data, such as glucose, LDL, hsCRP, or ferritin. |
| Biomarker reference data | Public metadata used to identify, display, format, and relate blood biomarkers. It includes fields such as marker ID, abbreviation, display name, unit, precision, and descriptions. |
| Extended biomarker | A supported biomarker represented in reference data that can be ingested, but does not have Optimal Zones. |
| Blood result data | Structured biomarker values associated with a test date or result context. Blood result data can come from structured API submission, document processing, or InsideTracker-managed lab testing. |
| Blood Result Upload (BRU) | The asynchronous workflow for uploading blood result documents, submitting a BRU process, and tracking processing until published results are available. |
| Add Blood Result | The structured API workflow for submitting discrete biomarker values, test date, and result context directly to InsideTracker. |
| Physiomarker | User-specific physiologic, activity, or sleep signal data, such as resting heart rate, steps, sleep duration, or VO2 max. Physiomarkers are health signals in their own right and can also support downstream outputs. |
| Physiomarker reference data | Metadata used to translate physio marker tags into display labels, units, categories, and precision. |
| Profile data | Supporting User context such as body measurements, baseline physiomarker profile data, and onboarding questionnaire context. |
| Questionnaire value sets | InsideTracker-supported options for onboarding questions such as dietary constraints, foods, supplements, exercise, lifestyle, desired focus, and related context. Use these values instead of hard-coding unsupported options. |
Inventory And Lab Connect
| Term | Meaning |
|---|---|
| Inventory | Your organization's inventory that can be assigned to Users. Inventory can affect workflow access, Lab Connect workflows, and output availability. |
| Assigned inventory | Inventory assigned to a User. Assignment can unlock or expose the workflow context needed for lab ordering, uploads, or outputs. |
| SKU | The inventory item identifier used when assigning or unassigning inventory. |
| Lab Connect | The InsideTracker-managed lab testing workflow for Quest Patient Service Center and Mobile Blood Draw testing. |
| Patient Service Center (PSC) | A Quest Diagnostics location where an eligible User completes the blood draw. |
| Mobile Blood Draw (MBD) | A lab testing path where a phlebotomist collects the User's blood sample at a supported location outside a Patient Service Center. |
| Panel | The set of biomarkers a Test is intended to measure. Assigned inventory determines the expected panel. |
| Test | In Lab Connect, the blood testing process for a User and panel. Current APIs may use testId and resultId interchangeably for the same assigned or resulted blood testing container. |
| Activation | The Lab Connect step that locks the assigned Test to the User and starts the InsideTracker-managed lab order workflow. |
| Order | The request created with the lab during activation so the User can complete sample collection for the Test. |
| Results | The biomarker data returned after the Test is fulfilled. Results include the container record and the individual biomarker results inside it. |
| Biomarker result | One measured biomarker value within Results. |
| Result ID | The API identifier for the Results container. In Lab Connect APIs, this can refer to the same underlying identifier as testId; it identifies the testing/result container, not a single biomarker. |
| Critical Results | Lab result values that require clinical follow-up. For InsideTracker-managed testing, critical-result outreach is handled through InsideTracker's lab-ordering vendor. |
Health Intelligence Outputs
| Term | Meaning |
|---|---|
| Output | User-facing InsideTracker content, calculation, or workflow generated from available User data, such as Inner Age, Category Scores, Recommendations, Action Plan, or ProTips. |
| Inner Age | A proprietary biological-age estimate based on blood biomarkers and body mass index, returned with confidence-aware result context. |
| Category Scores | Functional wellness scores that group biomarker and physiomarker data into areas such as metabolism, sleep, recovery, heart health, cognition, and inflammation. |
| Optimal Zones | Personalized blood biomarker ranges that help show how a User's marker value compares with InsideTracker target boundaries. |
| Recommendations | Personalized, evidence-based, non-prescription lifestyle guidance selected from InsideTracker's Knowledge Base for the User's biomarkers, goals, and context. |
| Impact Score | A recommendation ranking value that helps prioritize actions by evaluating relevant biomarkers, Scientific Grade, and goal association when goal context is available. |
| Scientific Grade | The evidence-strength value returned as gradeScore for a recommendation. It reflects source material that contributed to the recommendation and is used as part of Impact Score. |
| Action Plan | The workflow that turns recommendations into selected actions, schedules, notifications, goals, and check-ins. |
| Check-in | An adherence record for an Action Plan recommendation. Check-ins can be submitted manually or generated automatically when connected physio or activity data indicates adherence. |
| ProTip | A timely, concise, evidence-based insight triggered by InsideTracker to reinforce recommended actions or explain why guidance matters. |
| Supporting Research | Reference and science content that helps explain biomarkers and recommendation context. |
Events And Processing States
| Term | Meaning |
|---|---|
| Webhook event | An event notification sent by InsideTracker to your endpoint when processing, data onboarding, or generated content reaches a milestone. |
| BRU process | The asynchronous processing job created after one or more uploaded BRU files are submitted together. |
processId | Identifier for a BRU process. Store it to correlate status polling and webhook events. |
| Terminal state | A processing state that ends the current workflow, such as a BRU process reaching PUBLISHED or COMPLETE. |
| Published Results | Results that are available for downstream retrieval and output workflows. |
API Field Names
The API reference uses endpoint-specific field names such as testId, resultId, {resultId}, bloodTestId, or processId. Guides use descriptive terms first, then preserve exact API field names where they are required in a request, response, or path parameter.
Related Topics
- Authorization and Security
- Creating Users
- Inventory Management
- Lab Connect
- Blood Result Upload
- Add Blood Result
- Webhooks
Updated 28 days ago
Did this page help you?