Trainer Connect

Accepts the student's request and moves the class to the time they asked.

Accepts a student who asked to train with the trainer; they get access to the app.

Publishes a diet plan to the student (the previous active one is archived) and pushes them.

Adds one exercise to a training day of a program: sets, reps (or a range), load, rest.

Adds a library exercise to the trainer's favorites, shown first when building workouts.

Adds a food to the trainer's favorites, shown first when writing diet plans.

Adds a training day to a week of a program.

Adds a week at the end of a program (or at position).

Registers a supplement (or water) the student should take, with dose, times and days; the student gets reminders.

Runs any GET operation from list_operations as the connected trainer and returns the same JSON the app gets: a student's assessments, anamnesis, diet plan, workout history and sessions, check-ins, chat messages, contracts, financial metrics, the exercise library and more. Same permissions as the app.

Runs any POST, PUT, PATCH or DELETE operation from list_operations as the connected trainer, exactly as the app would: edit or archive workouts, assign programs, log or edit a session, create assessments, diet plans and check-ins, send chat messages, cancel or move classes, update the public page, and more. Same permissions, plan limits and validation as the app; a 422 lists what is missing. It can notify students (push, e-mail) and some operations cannot be undone, so confirm with the person first. Charges, refunds, payments, subscriptions, plans and prices, coupons, tabs, withdrawals, bank details, password and account deletion stay in the app.

Copies a catalog workout to one or more students; they see it in the app.

Approves every pending workout suggestion of one student at once, with one push.

Approves a student's suggestion and applies it to the exercise.

Hides an assessment from the student's history without deleting it.

Makes a team member responsible for a student; null removes it.

Turns an assessment without a student (trial class) into that student's first assessment.

Stops a person from sending messages to the trainer. Unblocking is in the app.

Cancels a class; the student gets a push, like in the app. Confirm with the person first.

Tells whether an address (slug) for the public page is free. Saves nothing.

Whether an e-mail already has an account in Trainer Connect, before inviting the student. Changes nothing.

Adds a comment to an idea.

Accepts a class a student booked that is waiting for confirmation.

Copies a plan or template to a student (student_id), or saves it as a template without student_id.

Duplicates a program, for another student (student_id) or as a new template (without student_id).

Answers a student's class change request with another time.

Creates a health questionnaire; send_anamnesis sends it to a student.

Saves a new physical assessment for a student: weight, body fat, circumferences (cm), skinfolds (mm), blood pressure. Send only what was measured.

Creates a periodic check-in (up to 20 questions); send_checkin assigns it to students.

Creates a challenge among students, with points per workout and per minute.

Writes a diet plan with meals and foods for a student (student_id), or a template without it. It starts as a draft: activate_diet_plan publishes it.

Adds a piece of equipment the trainer uses (e.g. a machine of their gym) to their own library. Returns the existing one if the name is taken.

Saves an exercise in the trainer's library, with instructions and optional video link.

Adds a food with macros per 100 g, or a dish from ingredients (macros are summed).

Creates a goal: workouts (number of workouts), frequency (per week), load (target kg in one exercise) or custom.

Adds a unit (branch) to the gym. Only the account owner can.

Blocks a date in the trainer's schedule (vacation, holiday).

Saves a reusable meal (name, time and foods) to drop into diet plans.

Adds a muscle group to the trainer's own library. Returns the existing one if the name is taken.

Creates a program (weeks with training days and exercises) for a student (student_id) or as a template without it. Weeks and days can also be added later.

Adds a recurring weekly class slot to the trainer's schedule, for a student or as a personal block without student_id.

Adds a student to the trainer's account, like "Adicionar aluno" in the app: the student gets an e-mail invite to install the app and see workouts. Name and e-mail are required; goal, weight, height, birth date and sex are optional. Respects the student limit of the trainer's plan.

Adds a training goal (e.g. "Corrida de rua") to the options the trainer picks from.

Creates a workout, assigned to a student (student_id) or as a template when student_id is empty, with its exercises: sets, reps (or a range with reps_max), load, rest, duration for cardio, notes. Exercises are matched to the Trainer Connect library by name so the student sees the demo video (or pass edb_exercise_id from search_exercises). For a weekly program, call it once per day with the same program name and day_of_week. The student is notified, like in the app.

Creates a temporary link (web and app) that lets someone see and copy a workout or one program day. Send workout_id or workout_day_id.

Declines a class a student booked that is waiting for confirmation; the student is told.

Shows what one Trainer Connect operation accepts: route parameters and the validation rules of each field (required, type, allowed values). Use it before api_write so the request is right the first time.

Find personal trainers listed in the public Trainer Connect directory (most are in Brazil; some are Brazilian trainers abroad), by specialty, name, city or state, and online or in-person. Specialties are written in Portuguese, e.g. "musculação", "emagrecimento", "funcional", "corrida", "hipertrofia". Returns up to 10 trainers with their public profile link. Contact details are never returned: the person talks to the trainer through the profile page.

Each student's current diet: published plans (since when, meals, adherence of the week) and drafts the trainer saved but never published to a student who has no active diet yet, with student name and the app_url of that student's diet screen. Use it to answer "who is still waiting for the diet I wrote?"; get_diet_plan shows the plan, and activate_diet_plan publishes it only after the trainer says so.

AI credits left for workout, diet and assessment generation in the app. Read only.