Adding Profile Data

Profile data is baseline context for your User's linked InsideTracker customer record. It helps InsideTracker personalize interpretation, recommendations, and output experiences.

Profile data does not replace blood results, lab ordering, or wearable data. It works alongside those inputs so InsideTracker can understand more about the User behind the health data.

Where This Fits

Use this page when you already have a linked InsideTracker customer record and a customer-level access token, and your next step is to add or update User context.

How Profile Data Supports Outputs

Profile data is supporting context. It does not replace the health data required by each product output; it helps InsideTracker interpret health data and personalize product experiences when the required data for those experiences is available.

What Belongs In Profile Data

Profile-related context spans account-level fields, body and physiomarker profile data, and onboarding questionnaire context. Use Customer Account Management for ongoing account-level changes.

Before You Begin

Use the sandbox environment while building and testing:

https://api.sandbox.insidetracker.com

Account-Level Fields

For account-level changes after creation, use Customer Account Management. Keep those updates separate from body measurement and questionnaire submissions.

Continue using the same User mapping and extId; do not create a new linked customer record for routine account edits.

Body And Physiomarker Profile Data

Use the physiomarker profile endpoint to add body composition, height, weight, and resting heart rate.

POST /api/pages/physioMarkers/physioMarkersPost
Content-Type: application/json
Authorization: Bearer {customer_access_token}

Example request:

{
  "bodyFatPercent": 25.5,
  "waist": 32,
  "hip": 38,
  "weight": 150,
  "height1": 5,
  "height2": 8,
  "rhr": 65
}

The API Reference includes the current request schema, accepted ranges, and response behavior for this endpoint.

Onboarding Questionnaire Context

The onboarding questionnaire endpoints collect lifestyle and preference context that can support personalization.

Use this pattern:

1. Fetch the supported value set for the questionnaire area.
2. Present the current values in your User experience.
3. Submit the User's selected IDs, values, or frequencies from those value sets with the customer-level access token.
4. Handle validation errors in your form experience.
5. Check onboarding status when your workflow needs to know whether the User has completed expected profile steps.

Use the onboarding status endpoint when your product experience needs to determine whether the User has completed the expected onboarding steps.

GET /api/customer/v1/onboarding/status
Authorization: Bearer {customer_access_token}

Woman Health Questionnaire

Woman health values are managed through customer-authenticated endpoints.

GET /api/customer/profile/woman-health
Authorization: Bearer {customer_access_token}

PATCH /api/customer/profile/woman-health
Content-Type: application/json
Authorization: Bearer {customer_access_token}

Use these endpoints when your onboarding flow collects reproductive stage, contraception, hormone therapy, or related woman health values. Use the API Reference for current payload fields and accepted reference values.

Questionnaire Value Sets

Use reference endpoints to populate onboarding form options. These endpoints return the value sets InsideTracker supports and that downstream outputs know how to interpret. Reference values can change, so fetch them from the API instead of treating this guide as the source of truth.

Best Practices

• Add profile data soon after creating the linked customer record when your product collects it during onboarding.
• Keep customer-level credentials and your User identity mapping synchronized.
• Convert measurement units before submitting body and physiomarker profile data.
• Fetch supported value sets for questionnaire options instead of hard-coding option lists.
• Keep account-level updates separate from body measurement and questionnaire submissions.
• Avoid logging sensitive profile data unless required for troubleshooting and allowed by your data-handling policies.

Implementation Checklist

• You have a customer-level access token for the linked customer record.
• You know which profile data your product experience collects.
• You know the User's measurement system before sending body measurements.
• You fetch supported value sets before displaying questionnaire options.
• You submit each questionnaire area to the correct endpoint.
• You check onboarding status when your flow depends on profile completion.
• You retrieve outputs only after the required inputs for that output are available.

Related API Reference