Customer Account Management

Customer Account Management keeps account-level fields aligned between your User record and the linked InsideTracker customer record. Use it when email, name, address, birth date, or gender changes after the User has already been created.

In these APIs, customer means the linked InsideTracker customer record for your User. Creating Users covers initial record creation and credential storage. Adding Profile Data covers body measurements, physiomarker profile data, and onboarding context used by downstream outputs.

Read account

Retrieve account-level information for the linked InsideTracker customer record.

Update account

Update the account field group that changed.

Keep records aligned

Keep your User records and linked InsideTracker customer records consistent.

Where This Fits

Use Customer Account Management after the User has a linked InsideTracker customer record. Account management is the maintenance path for account-level data after creation.

You already have	You do here	This supports
A linked InsideTracker customer record, stored customer-level credentials, and your User record	Retrieve or update account-level fields	Identity continuity, account maintenance, and workflows that rely on current account details

Before You Begin

Requirement	Why you need it
Customer-level token	Required for customer account endpoints.
Stored customer-level credentials	Required to retrieve or update the correct linked InsideTracker customer record.
Your User record	Required so your system remains the source of truth for the User relationship.
Updated account values	Required when a User's account-level information changes in your application.
Field-specific validation	Required because account updates use field-specific endpoints with their own request shapes.

Workflow

API operations are shown with the operation name followed by the method and path.

Retrieve the current linked account with Account information (GET /api/customer/v1/account/full) when you need readback or confirmation.
Decide which account field group changed in your User record.
Update only the changed field group through the matching endpoint.
Re-read account information when your application needs confirmation for display, audit, or downstream workflow decisions.
Keep body measurement, physiomarker, and onboarding context updates in Adding Profile Data rather than mixing them into account maintenance.

Endpoint Overview

Account task	Endpoint	Key request data
Account information	`GET /api/customer/v1/account/full`	No request body.
Change email	`PATCH /api/customer/account/change-email`	`newEmail`, `newEmailConfirm`.
Update name	`POST /api/pages/account/names-post`	`firstName`, `lastName`, `middleName`.
Update address	`POST /api/pages/account/address-post`	`countryAbbr`, `city`, `street`, `zipCode`, and optional address fields described in the API Reference.
Update birth date	`POST /api/pages/account/birth-date-post`	`birthdate`.
Update gender	`POST /api/pages/account/gender-post`	`gender`.

All Customer Account Management endpoints require customer-level authentication.

Account Fields

Field group	Use	Implementation note
Email	User account contact and identity continuity.	Email changes use a confirmation field. Keep your system and InsideTracker records aligned.
Name	User account identity.	Send the full request body required by the name endpoint.
Address	Account-level location and contact context.	Account address fields are separate from workflow-specific draw-location fields used by Lab Connect.
Birth date	Account-level demographic context.	Use the request format described in the API Reference.
Gender	Account-level demographic field exposed by the API.	Validate accepted values from the API Reference and avoid mapping unsupported free-form values. Do not assume this endpoint changes every sex- or gender-related field used by other workflows.

Account Information Response

The account information endpoint returns the current account-level data for the linked customer record. Use it for readback, reconciliation, or confirming an update.

The response can include fields that are not required for every workflow. Use the fields your integration needs and avoid building workflow logic from response fields that are not documented in the relevant workflow topic.

Implementation Guidance

Account update guidance

Treat customer in endpoint paths as the linked InsideTracker customer record for your User.
Update the field group that changed instead of sending unrelated account data.
Keep account-level fields separate from body measurements, onboarding questionnaire values, wearable data, and blood result data.
Re-read account information after updates when your application needs confirmation before continuing.

Implementation Checklist

You have a customer-level token for the linked InsideTracker customer record.
Your system stores the mapping between your User and the InsideTracker customer record.
Your application knows which account field group changed.
Your request includes all fields required by the matching endpoint.
Your application handles validation errors from field-specific account updates.
Your account data model stays separate from body measurement, onboarding, wearable, and blood result data.

Related API Reference

GET /api/customer/v1/account/full
PATCH /api/customer/account/change-email
POST /api/pages/account/names-post
POST /api/pages/account/address-post
POST /api/pages/account/birth-date-post
POST /api/pages/account/gender-post