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.

Identify markers

Retrieve marker IDs, abbreviations, names, descriptions, synonyms, and display metadata.

Format values

Use unit and precision metadata to display biomarker values consistently.

Connect context

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 caseEndpoints to useNotes
Display biomarker names, descriptions, abbreviations, and unitsGET /api/public/references/blood-markersPublic catalog of blood marker metadata.
Format or convert marker unitsGET /api/public/references/blood-marker-unitsUse with marker metadata when source or display units need confirmation.
Prepare Add Blood Result payloadsGET /api/public/references/blood-markers and GET /api/customer/blood/results-upload/available-markers-for-new-resultThe upload availability endpoint returns marker abbreviations; join those abbreviations to reference data to find marker IDs and metadata.
Build User-facing marker viewsGET /api/customer/v1/blood/markers-for-view and GET /api/public/references/blood-markersThe view availability endpoint returns marker abbreviations available for that User-facing context.
Explain blood and physio marker relationshipsGET /api/public/v1/markers/relationsUse 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.

EndpointUse it to...
GET /api/public/references/blood-markersRetrieve blood biomarker metadata such as ID, abbreviation, display name, unit, descriptions, synonyms, input ranges, and related physiomarkers.
GET /api/public/references/blood-marker-unitsRetrieve unit metadata and conversion factors for blood biomarkers.
GET /api/public/v1/markers/relationsRetrieve 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.

EndpointUse it to...
GET /api/customer/v1/blood/markers-for-viewRetrieve marker abbreviations available for User-facing blood marker views.
GET /api/customer/blood/results-upload/available-markers-for-new-resultRetrieve 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-markers
Common response fields
FieldDescription
idInsideTracker biomarker identifier. Use this when an API request requires markerId.
abbrBiomarker abbreviation, such as Glu. Availability endpoints commonly return marker abbreviations.
abbrForViewDisplay abbreviation when returned.
nameBiomarker display name.
fullNameFull biomarker name.
namingName variants for titles and sentences.
synonymsAlternate names Users or labs may recognize.
unitDefault display unit.
descriptionBiomarker description.
shortDescriptionShorter User-facing description.
precisionSuggested display precision.
minInputValue / maxInputValueInput bounds for submitted values.
relatedPhysioMarkerAbbrsRelated physiomarker abbreviations.
forGenderApplicability 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-units

Unit records include marker abbreviation, unit name, and conversion factor when available.

Implementation Pattern

When preparing structured blood result upload or biomarker display:

  1. Retrieve biomarker metadata from GET /api/public/references/blood-markers.
  2. Retrieve the workflow-specific marker availability list when needed.
  3. Match availability abbreviations to biomarker reference records by abbr.
  4. Use id when an API request requires markerId.
  5. Use unit, precision, minInputValue, and maxInputValue to validate and format values.
  6. 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 abbr to connect availability responses to reference data, and use id when submitting marker values that require markerId.
  • Use precision and 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-markers
  • GET /api/public/references/blood-marker-units
  • GET /api/public/v1/markers/relations
  • GET /api/customer/v1/blood/markers-for-view
  • GET /api/customer/blood/results-upload/available-markers-for-new-result
  • Related topic: Supported Biomarkers
  • Related topic: Optimal Zones
  • Related topic: Supporting Research

Did this page help you?