Heftig

Read a bounded summary of completed workouts in an inclusive calendar-date range (at most 366 days), newest first. Excludes active and abandoned workouts, photos, social data and notes. Narrow the date range if hasMore is true.

get_training_history

Read recorded meals and consumed nutrients for one exact local day in the user-supplied timezone. Incomplete totals are null; knownSubtotal is only the sum of known data. Never describe unknown nutrients as zero.

get_nutrition_day

Search Heftig canonical foods by exactly one query or barcode. Resolve ambiguous products with the user before previewing a meal. Nutrient null means unknown, never zero. Search results do not record a meal.

search_foods

Edit one existing meal explicitly selected by the user. Read get_nutrition_day first; use its entryId and latest revision. Resolve ambiguous meals before writing. Send the complete desired meal: omitted items are removed. Retain unchanged items with existing_item_id, without rematching them to the catalog. Quantity-only changes retain the unit and scale historical nutrients; explicit nutrient overrides describe the whole resulting quantity. New catalog items require preview_meal with entry_id and expected_revision. After reviewing the preview, send the unchanged original preview input meal, entry_id and expected_revision, plus its returned request_id and preview_hash. The normalized preview output meal is for display, not update input. Retained/snapshot-only edits need no preview. A conflict requires rereading and reconciling, never blindly overwriting. Retry timeouts with exactly the same request_id and input. Requires the separate nutrition:manage permission; log_meal only creates new meals.

update_meal

Permanently delete one existing meal and its items only when the user asks to delete that meal. Read get_nutrition_day first, resolve any ambiguous target with the user and use its entryId and latest revision. Other meals and saved meal templates are not deleted. Day totals reflect the removal. If the meal changed, reread and reconcile before retrying; never blindly replace the revision. Retry a timeout with exactly the same request_id and input. Requires the separate nutrition:manage permission.

delete_meal

Stateless preview of a new meal or changes to an existing meal. For an edit, first read get_nutrition_day and supply both entry_id and its latest expected_revision; existing_item_id references retain items of that same meal. Submit the complete desired meal: omitted items will be removed on update. New catalog items require this preview before log_meal or update_meal; snapshot/retained-only inputs may be saved directly. Snapshot nutrients describe the whole entered quantity. Ask for missing or ambiguous quantity, date or timezone. Show unknown nutrients as unknown. The returned request_id and preview_hash belong together; no meal or draft is stored.

preview_meal

Record one new meal the user asked to log. A meal containing only kind=snapshot items can be saved directly with a new request_id, without product search or preview_hash; nutrients describe each entire entered quantity. Catalog or mixed meals require the unchanged confirmed preview input and its request_id and preview_hash. Never invent missing amounts or nutrients: ask about ambiguous quantities and use null for unknown nutrients. Reuse exactly the same request_id and input after a timeout. A changed catalog meal requires a fresh preview. To change or remove an existing meal use update_meal or delete_meal instead.

log_meal

Make this owned plan the active plan, replacing the current active-plan choice. Call only when the user explicitly asks to activate or switch to this plan. Does not start or alter a workout. Supply a fresh UUID requestId; retries must reuse the same ID and planId. A completed retry returns its original result without reapplying a later superseded activation.

activate_training_plan

Create one complete inactive plan atomically in Heftig after the user requests saving it. Resolve exercises with search_exercises first and preserve their exact trackingMode. Supply a fresh UUID requestId for each intended creation; retry the identical requestId and plan after an uncertain result to avoid duplicates. Never reuse the ID for different content. Weights are combined kilograms even if weightPerHand is true; baseWeightKg is added once. At most 7 routines, 20 exercises per routine and 10 sets per exercise. Creates no workout and does not activate the plan; activation requires a separate explicit user request.

create_training_plan

Read the routines and planned sets of one plan owned by the connected user. Each routine includes a revision required for update_training_routine. For an existing exercise, its id is the saved routine entry ID; pass it as existingExerciseId to retain or adjust it without substituting its catalog reference. Weight is combined load in kilograms, including when weightPerHand is true; baseWeightKg is additive once. This does not read a running workout.

get_training_plan