Physiomarker Reference Data

Physiomarkers are non-blood physiological, activity, and behavioral signals that reflect a User's health. They are a meaningful data type on their own, and they can also help InsideTracker interpret blood biomarkers, health patterns, and output eligibility.

Physiomarker reference data is the supporting metadata that helps your application label, group, and explain those signals. It is not the same thing as User-specific physiomarker values.

Group signals

Retrieve physiomarker groups and display metadata.

Connect signals

Use marker relationships to connect blood biomarkers and physiomarkers.

Support context

Build explanatory views that combine behavior, physiology, and biomarker data.

Where This Fits

Use this page when your application needs reference metadata for physiomarkers: display names, group membership, group descriptions, and relationships between physiomarkers and blood biomarkers.

What Reference Data Supports

Use case	Reference data	Notes
Grouping related physiomarker signals	Physio marker groups	Use groups to organize signals such as steps or other physiomarker families.
Display support for returned physiomarker values	Wearables physiomarker references	Use tags, names, units, types, and precision when displaying returned physio values.
Blood and physio relationship context	Marker relationships	Show how blood biomarkers and physiomarkers relate when that context helps explain a health signal.
Category or output context	Category/reference fields and marker relationships	Category Scores may include physiomarker contributions. Keep score logic in Category Scores.

Before You Begin

Requirement	Why you need it
Physiomarker abbreviation, group, or returned tag	Required to map a signal to group or display metadata.
Reference endpoint plan	Use the endpoint that matches your display goal: group metadata, marker relationships, or wearable-service value display.
Missing-data handling	Not every User has connected wearable data, profile physiomarker data, or values for every physiomarker.

Physio Marker Groups

GET /api/public/references/physio-marker-groups

Use physio marker groups when you need group-level display metadata.

Common response fields

Field	Description
`id`	Physiomarker group identifier.
`abbr`	Group abbreviation, such as `STEPS`.
`name`	Display name.
`description`	Group description.
`primaryPhysioMarkerAbbr`	Primary physiomarker abbreviation for the group.
`includesMarkerAbbrs`	Physiomarker abbreviations included in the group.

Marker Relationships

GET /api/public/v1/markers/relations

Use marker relationships when you need to connect blood biomarkers and physiomarkers in explanatory UI.

Relationship response fields

Field	Description
`physioToBlood`	Relationship groups from physiomarkers to blood biomarkers.
`bloodToPhysio`	Relationship groups from blood biomarkers to physiomarkers.
`markerAbbr`	Marker abbreviation at the center of a relationship group.
`relations`	Related markers and relationship descriptions.

Implementation Pattern

Identify the blood biomarker, physiomarker, or category your UI needs to explain.
Use physio marker groups when you need group labels or group membership.
Use marker relationships when you need to connect blood and non-blood signals.
Use wearables physiomarker reference data when rendering returned physiomarker values.
Keep relationship context separate from personalized recommendations, Optimal Zones, and Category Scores.
Design for missing values and delayed wearable data.

Best Practices

Use reference endpoints instead of hard-coding physiomarker group names, membership, units, or relationship text.
Make clear whether a signal comes from profile data, wearable data, or another source when that matters for the User experience.
Treat relationship data as explanatory context, not as a scoring or recommendation model.
Design empty states for missing reference matches or missing User values.
Do not imply that every physiomarker is available for every User.

Related API Reference

GET /api/public/references/physio-marker-groups
GET /api/public/v1/markers/relations
GET /wearables/public/v1/reference-data/physio-markers