BTB Workout Log

Create or update rows in a training table. Each row without 'id' is inserted; with 'id' it updates your own row. Only data columns are accepted (user_id/timestamps/is_deleted are managed). weight is x100.

upsert_rows

Soft-delete (recoverable) your rows by id in a training table. Never a hard delete. Deleting a workout also deletes its exercises and sets; deleting a workout_exercise also deletes its sets — pass only the parent id.

soft_delete

Append historical workouts to the user's BTB account. Same date is merged; re-sending the same idempotency_key is a no-op. Expand rep schemes into individual sets. For exercises that don't exist yet, ALWAYS infer which muscles the movement trains from your own anatomy knowledge and include them as 'muscles' (1-3 entries): map each to an exact name from read_table('muscles'), with role 'primary' for the prime movers and 'secondary' for assisting muscles — never leave a new exercise without muscles, otherwise it won't appear in the muscle map. Archived exercises with a matching name are restored and reused automatically (reported in restored_exercises). The result includes a batch_id (revert with undo_import) and warnings: unmatched_muscles / exercises_created_without_muscles.

import_workouts

List the user's existing exercises. Reuse the exact 'name' values when importing so you don't create duplicates.

list_exercises

List past imports made through this API (batch id, created counts, date, whether already undone). Use to find the batch_id for undo_import.

list_imports

Read the user's workout records (most recent first), with exercises and sets (weight_kg, reps, duration_seconds, set_type). ALWAYS use this single tool to read, analyze or summarize training history — do not reconstruct history from read_table. To get a specific day (e.g. yesterday), set date_from and date_to to that date. Set include_ids=true only when you plan to update or delete specific records (ids feed upsert_rows / soft_delete).

list_workouts

Low-level row access to a training table (your own non-deleted rows), for looking up ids or preparing upsert_rows/soft_delete. For reading or analyzing workout history, use list_workouts instead (single call, nested JSON). Tables: workouts, workout_exercises, workout_sets, exercises, exercise_categories, muscles, exercise_muscles, exercise_category_assignments, workout_types. weight is stored x100 (e.g. 6000 = 60kg).

read_table

Restore (undo soft-delete) your rows by id in a training table. Restoring a workout (or workout_exercise) also restores the exercises and sets that were deleted together with it (see restored_workout_exercises / restored_workout_sets) — pass only the parent id.

restore

Revert an import made via import_workouts: soft-deletes the workouts/exercises/sets that the batch created (records merged into pre-existing workouts are kept). Confirm with the user before undoing.

undo_import