Optimal Zones

Optimal Zones are InsideTracker's personalized blood biomarker ranges. They help your application turn a raw marker value into User-facing context by showing where that value falls relative to personalized range boundaries.

In the API Reference, this surface appears as Blood marker ranges. The endpoint returns range boundary fields for supported blood biomarkers; your application combines those boundaries with marker values and biomarker reference data to build the User experience.

Personalize context

Retrieve range boundaries for a specific User with a customer-level token.

Display zones

Show where a marker value falls relative to personalized boundaries.

Use marker metadata

Pair ranges with biomarker names, units, and display precision.

Where This Fits

Optimal Zones are part of biomarker enrichment. Use them after your application has a linked User and needs to present blood marker values with personalized context.

Data Needed For This Output

Data	Required?	How InsideTracker receives it	Why it matters	If it is missing
Linked InsideTracker customer record and customer-level token	Required	Create the linked customer record for the User and store the returned customer-level credentials.	The range endpoint is a customer-level API.	Your application cannot retrieve User-specific range boundaries.
User profile context	Required	Creating Users and Adding Profile Data.	Optimal Zones are personalized to the User.	Your application may not have the User context needed for a personalized range request.
Blood marker values	Recommended for display	Add Blood Result, Blood Result Upload, OCR, or Lab Connect.	Marker values let your application show where the User falls relative to the returned boundaries.	Your application may be able to retrieve boundaries, but cannot show a User's actual marker position.
Biomarker reference data	Recommended for display	Retrieve with `GET /api/public/references/blood-markers` and `GET /api/public/references/blood-marker-units`.	Reference data provides display names, units, precision, descriptions, and marker metadata.	Your application may only be able to show raw marker IDs, abbreviations, and boundary values.

The Optimal Zones endpoint requires a customer-level access token. Requests made without customer-level authentication will fail authorization.

Retrieve Optimal Zone Boundaries

Use the customer blood ranges endpoint to retrieve personalized range boundaries.

GET /api/customer/blood/ranges
Authorization: Bearer {customer_access_token}

The response includes an items array. Each item represents one blood marker and the boundaries returned for that marker.

{
  "items": [
    {
      "markerId": 123,
      "markerAbbr": "Glu",
      "minBorderLine": 123.2,
      "minNearNormal": 133.2,
      "minA": 143.2,
      "minG": 153.2,
      "maxG": 163.2,
      "maxA": 173.2,
      "maxNearNormal": 183.2,
      "maxBorderLine": 193.2
    }
  ]
}

Response Fields

Range boundary fields

Field	Description
`items`	Personalized range entries returned for the User.
`markerId`	InsideTracker blood marker identifier.
`markerAbbr`	Blood marker abbreviation, such as `Glu`. Use biomarker reference data to map this to display names and units.
`minG` / `maxG`	Core Optimal Zone boundaries returned by the API.
`minA` / `maxA`	Broader normal or acceptable range boundaries returned by the API.
`minNearNormal` / `maxNearNormal`	Near-normal range boundaries returned by the API.
`minBorderLine` / `maxBorderLine`	Outer borderline boundaries returned by the API.

How To Use Range Boundaries

The boundary fields define the bands your application can use to place a User's marker value on an Optimal Zones display.

Boundary fields	How to use them
`minG` / `maxG`	The Optimal Zone for the marker. Values between these boundaries are inside the personalized target range.
`minA` / `maxA`	The broader normal or acceptable range around the Optimal Zone. Values between `minA` and `minG`, or between `maxG` and `maxA`, are typically presented as normal but outside the User's Optimal Zone.
`minNearNormal` / `maxNearNormal`	The next range outside the normal or acceptable range. Use these boundaries to show values that are near normal but farther from the Optimal Zone.
`minBorderLine` / `maxBorderLine`	The outer borderline boundaries returned by the API.

Treat these fields as display boundaries returned by InsideTracker. Do not recalculate them in your application or infer recommendation, risk, or diagnostic logic from the field names.

Display Guidance

Use Optimal Zones as a marker-level display layer:

Retrieve the User's blood marker values.
Retrieve Optimal Zone boundaries with GET /api/customer/blood/ranges.
Retrieve biomarker reference data for names, units, abbreviations, and precision.
Match marker values to range entries by marker ID or marker abbreviation.
Display the marker value, unit, and returned range boundaries together.

Output Availability

State	What it means	Application handling
Range entries returned	The API returned personalized boundaries for one or more markers.	Display ranges alongside matching marker values and units.
No matching range for a marker	The response does not include a range item for a marker your application wants to display.	Show the marker value without an Optimal Zone state, or use an empty state that avoids guessing the range.
User has no marker value	The range may be available, but the User has no corresponding value to compare.	Do not show the User's position in the zone until a marker value is available.

Best Practices

Implementation guidance

Use the returned range boundaries instead of hard-coding marker ranges.
Pair range boundaries with biomarker reference data for names, units, and precision.
Keep Optimal Zones separate from Category Scores, Inner Age, Recommendations, and Action Plan in your data model.
Refresh ranges when new blood results are added, and consider refreshing when User profile context changes.
Design for markers that have values but no returned range entry.
Use the API Reference for current schemas, nullable fields, and response behavior.

Implementation Checklist

You have a customer-level access token for the User.
The User has the profile context needed for personalized range retrieval.
Your application can retrieve or display blood marker values.
Your application retrieves biomarker reference data for marker names, units, and precision.
Your UI handles missing range entries without inventing boundaries.
Your data model keeps range boundaries separate from recommendation logic and other health intelligence outputs.

Related API Reference

GET /api/customer/blood/ranges
GET /api/public/references/blood-markers
GET /api/public/references/blood-marker-units
Related topic: Biomarker Reference Data
Related topic: Supported Biomarkers