Biomarker Reference Data
Use biomarker reference data to display blood biomarkers, units, input bounds, and marker relationships consistently.
Biomarker Reference Data
Biomarker reference data is the catalog layer for blood biomarkers in InsideTracker. It helps your application turn marker IDs and abbreviations into names, units, descriptions, input bounds, and related physiomarker context.
Use this page when your application needs to display biomarkers, prepare structured blood result uploads, format values, or connect biomarker data to other enrichment and output experiences.
Retrieve marker IDs, abbreviations, names, descriptions, synonyms, and display metadata.
Use unit and precision metadata to display biomarker values consistently.
Use marker relationships to connect biomarkers to broader health concepts.
Where This Fits
Biomarker Reference Data is supporting metadata for blood biomarker workflows. Use it anywhere your application needs to translate raw biomarker data into display, upload mapping, or explanatory context.
For example, a blood result upload workflow may start with a lab value and marker name from your system. Reference data helps your application map that source marker to an InsideTracker marker, confirm units and input bounds, and display the returned biomarker value consistently later.
What Reference Data Supports
| Use case | Endpoints to use | Notes |
|---|---|---|
| Display biomarker names, descriptions, abbreviations, and units | GET /api/public/references/blood-markers | Public catalog of blood marker metadata. |
| Format or convert marker units | GET /api/public/references/blood-marker-units | Use with marker metadata when source or display units need confirmation. |
| Prepare Add Blood Result payloads | GET /api/public/references/blood-markers and GET /api/customer/blood/results-upload/available-markers-for-new-result | The upload availability endpoint returns marker abbreviations; join those abbreviations to reference data to find marker IDs and metadata. |
| Build User-facing marker views | GET /api/customer/v1/blood/markers-for-view and GET /api/public/references/blood-markers | The view availability endpoint returns marker abbreviations available for that User-facing context. |
| Explain blood and physio marker relationships | GET /api/public/v1/markers/relations | Use relationship data for educational or contextual UI, not as a scoring model. |
Public Reference Endpoints
These endpoints provide general reference data and do not require a customer-level token.
| Endpoint | Use it to... |
|---|---|
GET /api/public/references/blood-markers | Retrieve blood biomarker metadata such as ID, abbreviation, display name, unit, descriptions, synonyms, input ranges, and related physiomarkers. |
GET /api/public/references/blood-marker-units | Retrieve unit metadata and conversion factors for blood biomarkers. |
GET /api/public/v1/markers/relations | Retrieve relationships between blood biomarkers and physiomarkers. |
User-Specific Availability Endpoints
These endpoints return marker abbreviations for a specific User or workflow and require customer-level authentication.
| Endpoint | Use it to... |
|---|---|
GET /api/customer/v1/blood/markers-for-view | Retrieve marker abbreviations available for User-facing blood marker views. |
GET /api/customer/blood/results-upload/available-markers-for-new-result | Retrieve marker abbreviations available for a new structured blood result upload. |
Because these endpoints return abbreviations rather than full marker metadata, use them with GET /api/public/references/blood-markers when your workflow also needs marker IDs, names, units, precision, or input bounds.
Blood Biomarker Metadata
Use the blood markers reference endpoint as the primary biomarker catalog.
GET /api/public/references/blood-markersCommon response fields
| Field | Description |
|---|---|
id | InsideTracker biomarker identifier. Use this when an API request requires markerId. |
abbr | Biomarker abbreviation, such as Glu. Availability endpoints commonly return marker abbreviations. |
abbrForView | Display abbreviation when returned. |
name | Biomarker display name. |
fullName | Full biomarker name. |
naming | Name variants for titles and sentences. |
synonyms | Alternate names Users or labs may recognize. |
unit | Default display unit. |
description | Biomarker description. |
shortDescription | Shorter User-facing description. |
precision | Suggested display precision. |
minInputValue / maxInputValue | Input bounds for submitted values. |
relatedPhysioMarkerAbbrs | Related physiomarker abbreviations. |
forGender | Applicability value returned by the API. |
Units And Relationships
Use marker units when you need to display or convert units consistently.
GET /api/public/references/blood-marker-unitsUnit records include marker abbreviation, unit name, and conversion factor when available.
Use marker relationships to understand how blood biomarkers and physiomarkers relate to one another.
GET /api/public/v1/markers/relationsThe response includes physioToBlood and bloodToPhysio relationship groups.
Implementation Pattern
When preparing structured blood result upload or biomarker display:
- Retrieve biomarker metadata from
GET /api/public/references/blood-markers. - Retrieve the workflow-specific marker availability list when needed.
- Match availability abbreviations to biomarker reference records by
abbr. - Use
idwhen an API request requiresmarkerId. - Use
unit,precision,minInputValue, andmaxInputValueto validate and format values. - Use descriptions, synonyms, and relationships only when your User experience needs additional context.
Best Practices
Implementation guidance
- Use reference endpoints instead of hard-coding biomarker names, units, or input bounds.
- Cache public reference data, but refresh it on a regular cadence.
- Join User-specific availability lists to public biomarker reference data before building upload or display workflows.
- Use
abbrto connect availability responses to reference data, and useidwhen submitting marker values that requiremarkerId. - Use
precisionand unit metadata to format values consistently. - Keep Category Scores, Optimal Zones, Recommendations, and Inner Age logic separate from raw biomarker reference data.
Related API Reference
GET /api/public/references/blood-markersGET /api/public/references/blood-marker-unitsGET /api/public/v1/markers/relationsGET /api/customer/v1/blood/markers-for-viewGET /api/customer/blood/results-upload/available-markers-for-new-result- Related topic: Supported Biomarkers
- Related topic: Optimal Zones
- Related topic: Supporting Research
Updated 27 days ago