Remaining Daily Intake

Optionally combine with Recommended Daily Intake and Daily Nutritional Goals to set targets, then update the remainder as the day progresses.

Plan & Token Requirements

Feature available in the following LogMeal Plans:

Accessible by the following User Types:

What It Does

Remaining Daily Intake returns the difference between the user's targets (from Daily Goals or Recommended Daily Intake) and their consumed intake today. It provides energy (kcal) and macro remainders by default; micronutrients are included when available on your plan and goals.

✕

✕

When to Use It / Outcomes

• You want to guide users during the day by showing how many kcal and nutrients remain for accomplishing their daily goals.
• You need to block or warn when users exceed ranges (e.g., sugar, sodium) or are below minimums (e.g., fiber, protein).
• You’re building coaching, meal suggestions, or nutrition scorecards driven by the user's progress.
• Output: JSON with remaining and over/under flags per nutrient for the current day in the user's timezone.

Feature-Specific Details

• Computation: Remaining = Target − ConsumedToday (per nutrient). Targets come from Daily Nutritional Goals when present; otherwise from GET /nutrition/getRecommendedDailyIntake.
• Time zone aware: "Today" is computed according to the user's current timezone; use history endpoints that already apply it.
• Ranges & warnings: Use the range and warning_range from the recommendation to mark good/attention/bad zones.
• Profiles matter: Sex, age, weight, height and lifestyle influence recommendations and auto‑computed goals.

Related Endpoints

Use these endpoints to compute and present Remaining Daily Intake:

• GET /nutrition/getRecommendedDailyIntake → 🔴 Provides recommended targets (and ranges) used as fallback or baseline.

• GET /daily_nutritional_goal → 🔴 Returns user personalized goals that override recommended targets.

• GET /history/getTotalIntakeByDay → ⚫ 🔴 🔵 Returns sum of today's consumed nutrients.

• GET /history/getTotalIntakeByDay/{date} → ⚫ 🔴 🔵 Same as above for a specific date (YYYY-MM-DD).

• Optional:

  • GET /history/getIntakesList → ⚫ 🔴 🔵 Detailed list of intakes between dates (for drill‑down UIs).

Typical Workflow

1. Ensure profile data (sex, age, weight, height, lifestyle) is set for the user.
2. Fetch targets by calling GET /nutrition/getRecommendedDailyIntake.
3. Fetch today's totals: call GET /history/getTotalIntakeByDay (or the dated variant).
4. Compute remaining per nutrient (target − consumed). Mark values against range/warning_range to highlight status.
5. Display results in your app and update whenever a new intake is logged or edited.