Client tracking

Client tracking powers the Tracking tab on a trainee’s card. It reads what the trainee logged in the app and returns computed views: adherence, statuses, personal records, trends and comparisons with the previous period. It also lets a coach add a weigh-in or a set of circumferences on the trainee’s behalf. For raw paged rows with no computation, see Tracking.


Source	`backend/apps/core-api/src/modules/client-tracking/`
Mounted in	`modules/clients/clients.routes.ts`, as `router.use('/:id/tracking', clientTrackingRouter(trackingController))`
Web lane base path	`/v1/web/clients/:id/tracking`
Bearer lane base path	`/v1/clients/:id/tracking`

The module has no entry of its own in modules/index.ts. It hangs off the clients router, which is mounted on both lanes, so every route below exists under both prefixes. The headings use the web lane path.

Auth and scoping

The router inherits two guards from the clients router:

withCoachAccess(ctx.prisma) resolves the caller’s coach permissions once per request.
requireAssignedClient(ctx.prisma) runs on every /:id path. A coach restricted to their own trainees gets NOT_FOUND for a trainee they are not assigned to, the same answer as for a trainee of another studio. A dismissed team member gets FORBIDDEN.

There is no requireRole guard. Inside the service, requireClient loads the trainee with studioId and deletedAt: null and throws NOT_FOUND (trainee not found) otherwise.

Shared rules

Dates and time zones

Every calculation works on civil dates (YYYY-MM-DD) in the trainee’s own time zone, resolved with resolveTimeZone(client.timezone, client.studio.timezone). “Today” is today for the trainee, not for the server. Weeks run Sunday to Saturday (weekStartIso).

Ranges

List views take a range query parameter.

string

default:"30d"

One of 7d, 30d, 3m. They map to 7, 30 and 90 days ending today (RANGE_DAYS).

A range is compared against the equal-length span that ends the day before it starts (previousWindow).

File plans

When the trainee’s active plan is a file plan (a PDF or a link, see Programs), there is nothing to measure against. The views return filePlan: true and null for the targets and adherence percentage, so the UI can show the file plan note instead of a grade.

Active plan lookup

repo.activeProgram(clientId, type) picks the most recently updated Program with status: ACTIVE and an exact type of TRAINING or NUTRITION. COMBINED programs are not considered here.

Endpoints

`GET /v1/web/clients/:id/tracking/summary`

The overview cards at the top of the Tracking tab. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

No query parameters. The windows are fixed:

Card	Window	Rule
`nutrition`	Last 30 days	`adherencePct` is the share of all 30 days whose status is `full`, see Nutrition day status. `null` for a file plan
`workouts.completedThisWeek`	Since Sunday	Logs with `completed: true`
`workouts.weeklyTarget`	Active training plan	`meta.workoutsPerWeek`, falling back to the number of plan days. `null` with no plan or a file plan
`workouts.averageSteps7`	Last 7 days	Mean of the days that have more than zero steps. `null` when none do
`weight.currentKg`	All time	Latest `WeightEntry`, falling back to `Client.weightKg`
`weight.deltaKg`	All time	Latest minus first entry, one decimal. `null` with fewer than two entries
`weight.waistCm`, `waistDeltaCm`	All time	Latest waist, and latest minus first
`appActivity`	Last 14 days	`full` when a meal or a workout session was logged that day, `light` when the app was only opened (`ClientAppDay`), otherwise `none`

A workout log counts as a session only when it is completed or has at least one done set (countsAsSession). Opening a workout and leaving is not a session. Response:

{
  "ok": true,
  "data": {
    "nutrition": { "adherencePct": 63, "loggedDays": 24, "totalDays": 30, "filePlan": false },
    "workouts": { "completedThisWeek": 2, "weeklyTarget": 4, "averageSteps7": 8421, "filePlan": false },
    "weight": { "currentKg": 78.4, "deltaKg": -3.1, "waistCm": 84.5, "waistDeltaCm": -2.5 },
    "appActivity": [
      { "date": "2026-09-23", "level": "full" },
      { "date": "2026-09-24", "level": "light" },
      { "date": "2026-09-25", "level": "none" }
    ]
  }
}

appActivity always has 14 entries, oldest first. The example is shortened. Errors: NOT_FOUND (trainee not found), UNAUTHORIZED.

`GET /v1/web/clients/:id/tracking/nutrition`

Per-day nutrition for a range, with adherence and a comparison to the previous period. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

string

default:"30d"

7d, 30d or 3m.

Eaten and target totals are not recomputed here. They come from partner.nutritionDays in the partner module, which already merges the plan, the trainee’s day snapshots and free-logged meals without double counting. That source refuses spans over 62 days, so a 3m range is fetched in chunks of 62 days (NUTRITION_CHUNK_DAYS). For each day the service adds:

status, see Nutrition day status.
meals: which of the four slots breakfast, lunch, dinner, snack have something logged. Plan meals map by type (snack_am, pre and post all count as snack). A plan meal counts when it was marked eaten outside, replaced, or has at least one eaten item. Custom meals count as snack. Free-logged MealLog rows have no meal type, so they map by local hour: before 11 is breakfast, before 16 is lunch, before 19 is snack, later is dinner.

The plan day for a date is found by rotation: nutritionDayIndexForOffset(dayCount, daysBetween(today, date)). Today is always the first plan day. unit is exchanges when the partner source reports mode: "mbp" for the first day, otherwise grams. In exchanges mode the protein, carbs and fat numbers are portions, not grams. Response:

{
  "ok": true,
  "data": {
    "range": "7d",
    "filePlan": false,
    "unit": "grams",
    "days": [
      {
        "date": "2026-10-05",
        "consumed": { "kcal": 1760, "protein": 142, "carbs": 168, "fat": 51 },
        "target": { "kcal": 1800, "protein": 150, "carbs": 160, "fat": 55 },
        "status": "full",
        "meals": ["breakfast", "lunch", "dinner"]
      },
      {
        "date": "2026-10-06",
        "consumed": { "kcal": 0, "protein": 0, "carbs": 0, "fat": 0 },
        "target": { "kcal": 1800, "protein": 150, "carbs": 160, "fat": 55 },
        "status": "none",
        "meals": []
      }
    ],
    "adherencePct": 57,
    "fullDays": 4,
    "overDays": 1,
    "loggedDays": 6,
    "totalDays": 7,
    "averageConsumed": { "kcal": 1812, "protein": 139.5, "carbs": 171.2, "fat": 56.3 },
    "averageTarget": { "kcal": 1800, "protein": 150, "carbs": 160, "fat": 55 },
    "previous": { "adherencePct": 43, "loggedDays": 5, "totalDays": 7, "overDays": 2 }
  }
}

adherencePct is fullDays / totalDays, rounded. The denominator is every day in the range, not only logged days. It is null for a file plan.
averageConsumed and averageTarget average over logged days only. Calories are rounded to whole numbers and macros to one decimal. Either is null when there is nothing to average.
previous is null when the previous span has no logged day. A span the trainee had not started logging in is not a baseline.

Errors: NOT_FOUND, VALIDATION (422) for an unknown range.

`GET /v1/web/clients/:id/tracking/nutrition/insight`

One AI-written Hebrew sentence that summarizes the nutrition data for the range. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

string

default:"30d"

7d, 30d or 3m.

The service runs the nutrition view without the previous-period comparison, then passes the range length, unit, logged, full and over day counts, and the two averages to createNutritionInsightGenerator (ai/nutrition-insight.ts). The generator uses OpenAI with the model in OPENAI_FORM_SUMMARY_MODEL, one retry and a 12 second timeout. sentence is null, with no model call, when OPENAI_API_KEY is not set, when no day is logged, or when there is no average. Caching: the result is cached in Redis for six hours under a key built from the trainee id and a SHA-1 hash of the input numbers. A new log changes the numbers and therefore the key, so a cached sentence never describes stale data. A cache read waits at most 300 ms and then falls through to the model. Only a real sentence is stored, so a failed call is retried on the next view. Response:

{
  "ok": true,
  "data": { "sentence": "..." }
}

sentence is a Hebrew string or null. Errors: NOT_FOUND, VALIDATION. A model failure does not raise. It returns sentence: null.

`GET /v1/web/clients/:id/tracking/nutrition/:date`

What the trainee logged on one day, meal by meal, as display lines. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

string

required

YYYY-MM-DD. Must be a real calendar date. 2025-02-30 is rejected.

The service loads the active nutrition plan, the trainee’s day snapshot (NutritionDayLog) and the MealLog rows of that day, then builds the list with describeLoggedNutritionDay. Three sources feed it, in this order:

Plan meals, id plan:<mealId>. A meal the trainee removed is skipped. For a replaced meal the line is the replacement’s name. For a meal eaten outside, every active item plus every added item is listed. Otherwise only items marked eaten are listed. A meal with no lines is left out. The food shown respects the trainee’s swap (a coach alternative or an automatic one) and their adjusted portion.
Custom meals, id custom:<mealId>. Uses the eaten added items, or the linked meal log’s items when none are marked. The slot comes from the log’s local hour, or snack without a log. Carries the log’s note and photoUrl.
Unlinked meal logs, id log:<logId>. Free logs not tied to a snapshot meal.

Food names and quantities come from the studio’s effective food rows: repo.foodsByIds overlays the per-studio override on each library food. Quantities are formatted for display, for example in household units where the food defines them, otherwise grams with a Hebrew gram suffix. For a file plan there is no plan day, so only custom meals and free logs appear. Response:

{
  "ok": true,
  "data": {
    "date": "2026-10-05",
    "meals": [
      {
        "id": "plan:ml_p9q8r7s",
        "slot": "breakfast",
        "label": null,
        "note": null,
        "photoUrl": null,
        "foods": [
          { "name": "Oats", "qty": "60 g" },
          { "name": "Greek yogurt", "qty": "1" }
        ]
      },
      {
        "id": "log:cmf2kb0qj0007qz8h5t6u7v8w",
        "slot": "dinner",
        "label": "Dinner out",
        "note": "Shared a pizza",
        "photoUrl": "https://media.example.com/meals/cmf2kb0qj.jpg",
        "foods": []
      }
    ]
  }
}

The qty strings in the example are illustrative. The real suffix is Hebrew. A meal with no label, no foods, no photo and no note is dropped. When a meal’s only food line has the same name as its label and no quantity, foods is emptied to avoid repeating the label. Errors: NOT_FOUND, VALIDATION for a bad date.

`GET /v1/web/clients/:id/tracking/workouts`

Workouts and steps for a range: an eight week grid, the session list, personal records, step stats and period KPIs. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

string

default:"30d"

7d, 30d or 3m.

How each part is built:

weeks: the last eight Sunday to Saturday weeks, oldest first, regardless of range. Each lists the completed workouts in that week.
logs: sessions inside the range, newest first. A log with no done set and not completed is an abandoned start and is left out. status is completed or partial.
volume: the sum of weight times reps over done sets that have both, rounded.
personalRecords: the five most recent records in the range, newest first. See Personal records.
steps.goal: the plan’s daily steps when the training plan’s movement requirement includes steps, otherwise Client.stepsGoal, otherwise null.
steps.days: the last seven days. steps is null for a day with no synced row.
steps.source: appleHealth when Client.lastCheckInPlatform is ios, healthConnect for android, otherwise null.
kpis.expected: weeklyTarget * rangeDays / 7, rounded. null without a weekly target.
kpis.totalVolume counts every session. kpis.averageDurationSec averages completed sessions that have a positive duration.
previous: the same stats for the previous period, or null when it has no session.

Response:

{
  "ok": true,
  "data": {
    "range": "30d",
    "filePlan": false,
    "weeklyTarget": 4,
    "weeks": [
      {
        "weekStart": "2026-10-04",
        "weekEnd": "2026-10-10",
        "completed": 1,
        "workouts": [{ "date": "2026-10-04", "name": "A" }],
        "isCurrent": true
      }
    ],
    "logs": [
      {
        "id": "cmf2kc4tn000bqz8h1a2b3c4d",
        "date": "2026-10-04",
        "name": "A",
        "status": "completed",
        "durationSec": 3180,
        "volume": 8420,
        "sets": 18,
        "exerciseCount": 6
      }
    ],
    "personalRecords": [
      {
        "exercise": "Bench press",
        "date": "2026-10-04",
        "weight": 82.5,
        "reps": 6,
        "previous": { "weight": 80, "reps": 6 }
      }
    ],
    "steps": {
      "goal": 8000,
      "days": [
        { "date": "2026-10-05", "steps": 9120 },
        { "date": "2026-10-06", "steps": null }
      ],
      "average": 8421,
      "daysOnTarget": 4,
      "today": null,
      "lastSyncedAt": "2026-10-05T18:40:11.000Z",
      "source": "appleHealth"
    },
    "kpis": {
      "completed": 13,
      "expected": 17,
      "totalVolume": 104300,
      "averageDurationSec": 3240,
      "personalRecords": 3
    },
    "previous": { "completed": 11, "totalVolume": 96100, "averageDurationSec": 3310 }
  }
}

weeks always has eight entries and steps.days seven. The example is shortened. kpis.personalRecords is the count of all records in the range, while the personalRecords array holds at most five. Errors: NOT_FOUND, VALIDATION.

`GET /v1/web/clients/:id/tracking/workouts/:logId`

One workout session in detail, compared with the earlier sessions of the same plan day. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

string

required

The WorkoutLog id. Must belong to this trainee.

“Same type” sessions are found by repo.workoutLogsOfType: logs with the same dayId, or, for logs written before dayId was stored, the same label inside the same program. The service scans up to 40 of them, newest first, up to and including this log’s performedOn. Per exercise (only exercises with at least one done set):

sets: the done sets, each with weight, reps and targetReps.
best: the top set of this session, by weight and then reps, among sets with reps above zero.
isPersonalRecord: this session’s record-eligible best beats the trainee’s best from every log before this one (up to 500 logs). See Personal records.
previousBest: the best set of the same exercise in the most recent earlier session of the same type, or null.
deltaKg: the difference in weight against previousBest, when both sets carry weight. Otherwise null.
deltaReps: the difference in reps, used when the comparison is not weighted. Otherwise null.

Response:

{
  "ok": true,
  "data": {
    "id": "cmf2kc4tn000bqz8h1a2b3c4d",
    "date": "2026-10-04",
    "name": "A",
    "status": "completed",
    "note": null,
    "kpis": { "durationSec": 3180, "volume": 8420, "sets": 18, "personalRecords": 1 },
    "exercises": [
      {
        "name": "Bench press",
        "sets": [
          { "weight": 80, "reps": 8, "targetReps": 8 },
          { "weight": 82.5, "reps": 6, "targetReps": 6 }
        ],
        "best": { "weight": 82.5, "reps": 6 },
        "isPersonalRecord": true,
        "previousBest": { "weight": 80, "reps": 6 },
        "deltaKg": 2.5,
        "deltaReps": null
      }
    ],
    "volumeHistory": [
      { "id": "cmf1zz9aa0009qz8h1a2b3c4d", "date": "2026-09-27", "volume": 8100, "durationSec": 3300, "isCurrent": false },
      { "id": "cmf2kc4tn000bqz8h1a2b3c4d", "date": "2026-10-04", "volume": 8420, "durationSec": 3180, "isCurrent": true }
    ],
    "previousSessions": [
      { "id": "cmf1zz9aa0009qz8h1a2b3c4d", "date": "2026-09-27", "durationSec": 3300, "volume": 8100, "status": "completed" }
    ]
  }
}

volumeHistory holds this session and up to seven earlier ones, oldest first. previousSessions holds up to five earlier ones, newest first. Errors: NOT_FOUND (trainee not found or workout not found).

`GET /v1/web/clients/:id/tracking/weight`

Weight trend, goal progress and circumferences. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

string

default:"30d"

7d, 30d or 3m. Filters points, log and circumferences.history. The start, current and delta values use every weigh-in ever recorded.

startKg is the first WeightEntry, currentKg the latest. Both fall back to Client.weightKg when there are no entries.
deltaKg is current minus start, and needs at least two entries.
goal comes from goalProgress(start, current, goal). direction is lose when the goal is below the start, otherwise gain. pct is (start - current) / (start - goal) as a percentage, clamped to 0 through 100. With a missing value, or when start equals goal, pct and direction are null.
weeklyRateKg is the change between the first and last point in range, scaled to seven days. null with fewer than two points or less than a day between them.
weighInEveryDays is the span in days between the first and last point in range divided by the number of gaps.
Each point’s deltaKg is against the previous weigh-in, across the full history.
source is one of app, coach, form, automation, import, from weighInSource. A row with a formResponseId or source form is form. COACH is coach. automation is automation. A source starting with autofit is import. Everything else, including rows with no source, is app.
circumferences.tiles has one entry per key in the fixed order chest, waist, hips, arm, thigh. delta is latest minus first over all time. improving is true when the value moved in the wanted direction: up for arm, down for the rest. Both are null with fewer than two values, and improving is null for a zero delta.

Response:

{
  "ok": true,
  "data": {
    "range": "30d",
    "startKg": 81.5,
    "currentKg": 78.4,
    "deltaKg": -3.1,
    "goalKg": 75,
    "goal": { "pct": 48, "remainingKg": 3.4, "direction": "lose" },
    "weeklyRateKg": -0.4,
    "weighInEveryDays": 3.5,
    "points": [
      {
        "id": "cmw00010qz8h1a2b3c4d5e6f",
        "date": "2026-10-01",
        "weightKg": 78.9,
        "deltaKg": -0.3,
        "isFirst": false,
        "note": null,
        "source": "app"
      },
      {
        "id": "cmw00020qz8h7g8h9i0j1k2l",
        "date": "2026-10-05",
        "weightKg": 78.4,
        "deltaKg": -0.5,
        "isFirst": false,
        "note": "Weighed at the studio",
        "source": "coach"
      }
    ],
    "log": [],
    "circumferences": {
      "tiles": [
        { "key": "chest", "current": 101, "delta": -1.5, "improving": true },
        { "key": "waist", "current": 84.5, "delta": -2.5, "improving": true },
        { "key": "hips", "current": null, "delta": null, "improving": null },
        { "key": "arm", "current": 36, "delta": 0.5, "improving": true },
        { "key": "thigh", "current": null, "delta": null, "improving": null }
      ],
      "history": [
        { "date": "2026-10-05", "values": { "waist": 84.5, "arm": 36 }, "note": null }
      ]
    }
  }
}

points is oldest first. log is the same list newest first (emptied in the example). history is newest first and only includes days that carry at least one of the five circumference keys. Errors: NOT_FOUND, VALIDATION.

`POST /v1/web/clients/:id/tracking/weights`

Adds a weigh-in on the trainee’s behalf. Returns 201. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

number

required

Coerced to a number. Positive, maximum 500.

string

YYYY-MM-DD, a real calendar date. Defaults to today in the trainee’s time zone.

string

Trimmed, maximum 500 characters.

A WeightEntry is created with source: "COACH". For today, recordedAt is the current instant. For an earlier date it is local noon of that day, so the civil day survives later time zone conversions. Side effect: Client.weightKg is updated to the new value when this entry is the latest one, that is when there was no earlier entry or recordedAt is at or after the previous latest. A back-dated weigh-in older than the latest leaves it alone. No activity record or notification is written. Response:

{
  "ok": true,
  "data": {
    "id": "cmw00020qz8h7g8h9i0j1k2l",
    "weightKg": 78.4,
    "recordedAt": "2026-10-05T09:00:00.000Z",
    "source": "COACH",
    "note": "Weighed at the studio"
  }
}

Errors: BAD_REQUEST (the date cannot be in the future). NOT_FOUND. VALIDATION for a bad body.

`POST /v1/web/clients/:id/tracking/measurements`

Adds circumferences for a day on the trainee’s behalf. Returns 201. Auth: web lane or bearer lane, behind requireAssignedClient.

string

required

The trainee id.

string

YYYY-MM-DD. Defaults to today in the trainee’s time zone.

number

Centimetres. Coerced, positive, maximum 300.

number

Same rule.

number

Same rule.

number

Same rule.

number

Same rule.

string

Trimmed, maximum 500 characters.

At least one of the five measurements is required. The values are merged into that day’s DailyMetric.measurements JSON, the same way the trainee app writes them. Keys already recorded that day, including ones this route does not know such as a neck value, are kept. Only the keys sent are overwritten. If the day already has a different note, the coach’s note is appended on a new line. The row is upserted on (clientId, date). Response:

{
  "ok": true,
  "data": {
    "date": "2026-10-05",
    "values": { "waist": 84.5, "arm": 36 },
    "note": null
  }
}

values returns only the five circumference keys, even when the stored JSON holds more. Errors: BAD_REQUEST (the date cannot be in the future). NOT_FOUND. VALIDATION for a bad body, including at least one measurement is required.

Computation rules

All of these live in client-tracking.compute.ts as pure functions on civil dates, so they can be tested without a clock or a database.

Nutrition day status

nutritionDayStatus(consumed, target) compares calories only.

Status	Rule
`none`	Nothing logged: kcal, protein, carbs and fat are all zero
`noTarget`	Logged, but there is no target or its kcal is zero or less
`over`	Consumed kcal is more than 115% of the target (`OVER_RATIO`)
`full`	Consumed kcal is at least 90% of the target (`FULL_MIN_RATIO`)
`partial`	Below 90%

Personal records

A record is judged per exercise. Exercises are matched on exerciseId. A logged row with no id is matched on its name instead (name:<name>).

Which sets are eligible (countsForRecord). The set must have reps above zero. A set with no weight, or with no target reps, always counts. A weighted set with a target counts only when the reps reached at least 80% of the target (RECORD_MIN_REPS_PERCENT).
Best set (bestSet). Among eligible sets, the heaviest, with reps as the tie-break (outranks).
Beating a record (beatsRecord). If either set carries weight, the new weight must be strictly higher. Reps alone never beat a weighted record at the same weight. If neither carries weight (bodyweight work), more reps wins.

In the workouts view the baseline is the trainee’s best per exercise from up to 500 logs before the range. The service then walks the range oldest first, records each session that beats the running best, and raises the running best as it goes. An exercise with no earlier best cannot produce a record, so a first ever session never counts as one.

Workout status

workoutStatus(completed, doneSets) returns completed when the log is completed, partial when it has at least one done set, and null otherwise. Only sets with done: true in the app-written entries JSON are read at all.

Who else uses this module

Other modules import the pure helpers from client-tracking.compute.ts, so the coach views and the rest of the product agree on one definition:

modules/checkins/checkins-insights.ts and modules/checkins/checkins-tracking.ts, which also uses the NutritionDaysSource type from the service.
modules/trainee/trainee.service.ts and modules/trainee/measurements-summary.ts (weighInSource).
modules/inbox/context-video.ts (parseExercises) and modules/inbox/context-activity.ts (appActivityLevels, weekStartIso).

API basics

Trainees

Plans and libraries

Tracking

Imports

Forms

Tasks and automation

Communication

Studio and billing

Admin and internal services

Trainee app API

Partner and automation

Public, internal and auth

Client tracking

Auth and scoping

Shared rules

Dates and time zones

Ranges

File plans

Active plan lookup

Endpoints

`GET /v1/web/clients/:id/tracking/summary`

`GET /v1/web/clients/:id/tracking/nutrition`

`GET /v1/web/clients/:id/tracking/nutrition/insight`

`GET /v1/web/clients/:id/tracking/nutrition/:date`

`GET /v1/web/clients/:id/tracking/workouts`

`GET /v1/web/clients/:id/tracking/workouts/:logId`

`GET /v1/web/clients/:id/tracking/weight`

`POST /v1/web/clients/:id/tracking/weights`

`POST /v1/web/clients/:id/tracking/measurements`

Computation rules

Nutrition day status

Personal records

Workout status

Who else uses this module

​Auth and scoping

​Shared rules

​Dates and time zones

​Ranges

​File plans

​Active plan lookup

​Endpoints

​GET /v1/web/clients/:id/tracking/summary

​GET /v1/web/clients/:id/tracking/nutrition

​GET /v1/web/clients/:id/tracking/nutrition/insight

​GET /v1/web/clients/:id/tracking/nutrition/:date

​GET /v1/web/clients/:id/tracking/workouts

​GET /v1/web/clients/:id/tracking/workouts/:logId

​GET /v1/web/clients/:id/tracking/weight

​POST /v1/web/clients/:id/tracking/weights

​POST /v1/web/clients/:id/tracking/measurements

​Computation rules

​Nutrition day status

​Personal records

​Workout status

​Who else uses this module

Auth and scoping

Shared rules

Dates and time zones

Ranges

File plans

Active plan lookup

Endpoints

`GET /v1/web/clients/:id/tracking/summary`

`GET /v1/web/clients/:id/tracking/nutrition`

`GET /v1/web/clients/:id/tracking/nutrition/insight`

`GET /v1/web/clients/:id/tracking/nutrition/:date`

`GET /v1/web/clients/:id/tracking/workouts`

`GET /v1/web/clients/:id/tracking/workouts/:logId`

`GET /v1/web/clients/:id/tracking/weight`

`POST /v1/web/clients/:id/tracking/weights`

`POST /v1/web/clients/:id/tracking/measurements`

Computation rules

Nutrition day status

Personal records

Workout status

Who else uses this module