Skip to main content
Available capabilities depend on enabled features, scopes, and connection grants.

2026-11-20 - Cancel, approve, sell memberships and manage payments through MCP (upcoming)

Coaches can cancel bookings and calendar events, approve or reject registration, retention and membership requests, sell and cancel memberships, and send or cancel payment requests. New read tools list payment requests, transactions, chargebacks, credit overdrafts and dashboard to-dos. Coaches can also manage to-dos and notification status, update event templates, create member tags and assign intake forms. Each write requires its own grant and user confirmation. The nutrition_plans module now requires health data consent. See Tools. Coaches can publish and edit booking links, trace each signup to its CRM lead, record follow-up, and book a trial. They can also page through CRM leads by location, correct contact details, and transfer a lead between locations they can access. Coaches can also manage individual booking series, correct existing booking payments, and preview and generate invoices for selected bill-later lessons. Each write requires its own grant and user confirmation. See Booking links and leads, Recurring bookings, Bookings, and Bill-later lessons.

2026-11-19 - Manage bill-later lessons through MCP (upcoming)

The company/coach lesson_billing module reads bill-later lesson prices, statuses and linked records, and previews eligible credits for an open lesson. With an explicit write grant and confirmation, a coach can change the unit price or settle the lesson using a selected credit pack or membership. A date-range overview lists bookings that are still set to bill later and due credit deductions, including any recorded wait reason. See Bill-later lesson tools.

2026-11-18 - Change membership locations through MCP (upcoming)

update_subscription_home_location sets a company location on an existing membership and its linked subscription. It requires an explicit write grant and user confirmation. The location applies to future billing. See Subscription tools.

2026-11-17 - Google Health account linking and notifications (upcoming)

Health account linking accepts the google_health provider. Google Health notifications support subscriber verification and signed data-change delivery at /public/v1/webhooks/health/google_health. Connector availability and each client’s consent determine access. See the API reference.

2026-11-16 - Edit nutrition templates and plan days through MCP (upcoming)

set_nutrition_plan_item and preview_nutrition_plan_item_change now work on company nutrition plan templates when clientId is omitted, and accept dayNumber to change one day of a multi-day plan. Legacy nutrition plans and templates can now have up to 28 days. The new duplicate_nutrition_plan tool copies a template or a client’s plan into a new template. Training plan day, exercise and activity tools also accept a client’s assigned plan. See Nutrition plan tools and Training tools.

2026-11-13 - Bulk intake answers, member follow-up and attendance filter (upcoming)

The new list_intake_submissions MCP tool reads submitted intake forms of many members at once, filtered by submission date and optionally by member or question text. get_client now includes the member’s follow-up date, source and assigned coach. list_bookings can filter on attendance (Attended, DidNotAttend, NoStatus). See Intake tools, Client tools and Booking tools.

2026-11-13 — Add several exercises to a superset (upcoming)

PATCH /public/v1/workout/plans/template/{planId}/moments/{planMomentId}/supersets/{groupId}/exercises and PATCH /public/v1/workout/performance/sessions/{sessionId}/supersets/{groupId}/exercises accept exerciseIds, an array of catalog exercise IDs added to the superset in array order in a single request. The request is all-or-nothing and cannot be combined with planExerciseId, performanceId or exerciseId. Existing requests are unchanged. See the API reference.

2026-11-08 - Public API access application (upcoming)

Companies can request Public API access from the coach dashboard by describing their intended use, software and any external developer. Valid applications are approved automatically once per company, enabling credential and webhook creation. Companies with access already enabled keep their existing access. See the Public API quickstart.

2026-11-06 — MCP usage guidance and quota visibility (upcoming)

MCP initialization and discovery instructions state the configured request allowances. Transport responses include quota, remaining-capacity, and reset headers; HTTP 429 responses include the applied limit and retry delay. Default allowances are 120 requests per minute per credential and 240 per IP. The separate weighted tool query budget still applies. See Connection & Protocol. Every tool description also includes the current shared quotas, retry guidance, read/write requirements and applicable pagination, date-window, confirmation and side-effect guidance. Function-calling clients can forward these descriptions with the tools’ names and schemas to make the guidance visible to their models.

2026-11-05 — MCP bill-later bookings (upcoming)

The company/coach create_booking tool accepts paymentMethod: "billLater" for later invoicing at the configured session price, without deducting credits at booking creation. The default remains product; free is also supported. See Booking tools.

2026-11-04 — Scheduled training-plan visibility (upcoming)

Training-plan assignments accept hideUntilStartDate: true with a start date. The assigned copy becomes visible and available to the client at midnight on that date in the company timezone. Coach access remains available. Existing assignments keep their current availability; paused plans remain paused. Use scheduleStartDate on the workout assignment API endpoints or startDate with the MCP assign_workout_plan tool. MCP plan summaries include the UTC clientAvailableFrom time. See Training tools and API reference.

Upcoming release — Include entered workout sets on completion

PATCH /public/v1/workout/performance/sessions/{sessionId}/complete accepts confirmUnconfirmedSets: true when a coach completes an assigned-plan workout. Fully entered numeric sets are included in the completion; empty, incomplete and prescribed-range rows remain unconfirmed. Freestyle, WOD and group sessions do not support this option. Omitting it preserves the existing behavior. The operation requires workout_sessions:write. Set changes and completion succeed together, and retries preserve an already completed session’s set states. See the workout operations in the API Reference.

2026-11-04 — MCP member tags (upcoming)

The company/coach clients module adds update_client_tags to add or remove existing company tags from one member. Other tags are preserved. The tool requires its own write grant, current member update permission and an idempotencyKey. Existing grants remain unchanged. See Client tools.

2026-11-04 — MCP intake form assignment status

The MCP intake module adds get_client_intake_assignments. For up to 50 clients at once it returns whether an intake form is currently assigned and its status (not_assigned, assigned, in_progress or submitted), with the form name, assignment date and submission date. Use it to check before a trial session which prospects still need to complete or be assigned an intake. Existing grants with the intake module include the tool. See Intake tools.

2026-11-02 — MCP agenda activities

Company/coach MCP adds create_calendar_event and update_calendar_event for lessons and appointments with templates, locations and trainers. Bounded daily, weekly and monthly recurrence is supported. Updates explicitly target one event, one occurrence, this and following occurrences, or an entire series. Both tools require individual write grants, current calendar permissions, confirmation and an idempotency key. Existing grants are unchanged. See Calendar event tools.

2026-11-02 — Weekly ranking filters (upcoming)

GET /public/v1/workout/clients/{clientId}/weekly-ranking accepts three optional, combinable query parameters:
  • gender: male, female or prefer_not_to_say (members without a stated gender or with gender “Other”).
  • scoringType: standard, forTime, amrap, emom, tabata or maxLoad. The board is ranked by the XP earned from WODs of that scoring type only.
  • allowedDivisions: rx, scaled or rx_scaled. The board is ranked by the XP earned from WODs that allow exactly those divisions.
Ranks, podium, list, the client’s own row and counts are calculated within the filtered board, and the response shape is unchanged. Responses also include availableFilters (an object keyed by filter name, each listing { key, label } options with translated labels) and selectedFilters. An unsupported value returns 400 LEADERBOARD_FILTER_INVALID. See the workout operations in the API Reference.

Upcoming release — Member branches and customer imports in MCP

Company staff can list eligible home branches, view a member’s assignment and change or clear it with explicit confirmation. create_client also accepts an optional home branch. Current company member/location permissions apply. The optional imports module supports CSV/XLSX member uploads, column mapping, canonical previews, approved row selection, background status/history and queued cancellation. Map homeLocation per row or choose a default branch for blank values. Existing assignments are preserved when no branch is supplied. Imports require access to all company members/locations and the appropriate import permissions. Each write needs a separate MCP grant; existing connections do not receive new write actions automatically. See home branches and customer imports.

Upcoming release — Default agreement message

Company membership settings support registrationSigning.defaultMessages, with plain-text variants in English, Dutch, German, French and Spanish, up to 2000 characters per language. The member’s language is preselected when a coach sends an agreement; the coach can change the language and edit or clear the message. An empty variant uses the translated system default in the same language. The company settings MCP operation accepts the same variants; omitted languages retain their saved messages. The former single-message field remains readable. Signing links use the configured validity of 1 to 90 whole days, with 14 days as the default. Existing links retain their expiry date.

2026-10-27 — Complete MCP collection pages (upcoming)

list_client_checkups, list_checkup_forms, list_client_habits, list_habit_templates, get_habit_entries, list_measurement_types, get_client_credits and list_calendar_events accept optional page and limit and return page, limit and total. Pages hold 10 records by default and at most 100; request the next page while page * limit < total. Callers that omit limit now receive 10 records per page instead of up to 100. get_client_credits.totalAvailable and get_habit_entries.periodSummary cover the complete selection, independent of the page. Calendar ranges too large to expand completely return COMPANY_MCP_CALENDAR_QUERY_TOO_COMPLEX, and habit summaries above 5,000 periods return COMPANY_MCP_HABIT_SUMMARY_TOO_LARGE. list_subscriptions search covers every matching client in the company. The client AI tools client_ai_get_my_credits, client_ai_list_my_habits, client_ai_get_my_habit_entries, client_ai_list_my_measurement_types and client_ai_list_my_checkups page the same way.

2026-10-27 — Member status automation and history (upcoming)

PATCH /public/v1/clients/{clientId}/lifecycle accepts relationshipStatusMode: "manual" | "automatic". Status edits default to manual protection, respected when enabled by company policy. Automatic mode resumes company status rules without changing explicit portal restrictions. Read or update company event rules with GET or PATCH /public/v1/clients/status-automation and the separate client_status_automation:read or client_status_automation:write scope. Writes merge supplied rules and apply to future events. Client reads include relationship.statusMode; the client timeline includes recorded status-change provenance. The MCP clients module adds get_member_status_automation, update_member_status_automation, list_client_status_history and update_client_lifecycle. Each write requires a separate explicit grant and an idempotency key. See client statuses and app access.

2026-10-27 — Shared member field management (upcoming)

Manage individual shared member field definitions with POST /public/v1/client-custom-fields and PATCH or DELETE /public/v1/client-custom-fields/{fieldKey}. Read the complete library with GET /public/v1/client-custom-fields/library. These operations use the separate client_custom_field_definitions:read and client_custom_field_definitions:write scopes; existing member-value scopes retain their meaning. MCP adds list_client_custom_fields, create_client_custom_field, update_client_custom_field, delete_client_custom_field and update_client_custom_field_values. Each write requires its own grant and an idempotency key. Removing a used definition preserves its member values. See shared field management and MCP tools.

Upcoming release — Invoice and credit-note automation

GET /public/v1/finance/invoices/{invoiceId}/accounting returns one complete invoice or credit note, including all lines, signed amounts, recorded totals, available issuer and recipient identities, ledger references, original invoice number and reconciliation warnings. It requires finance_invoices:read. Original PDFs remain available separately with finance_invoice_pdfs:read. Existing invoice list and detail responses are unchanged. Make accounting connections can request finance_invoice_webhooks:read and finance_invoice_webhooks:write for invoice.created subscriptions through /public/v1/make/accounting. This event covers both invoices and credit notes. These scopes require fresh company consent and do not request health-data or private-communication access. Existing grants retain their approved permissions. Zapier and n8n accounting connections can request the same limited permissions and manage invoice-only notifications through /public/v1/zapier/accounting and /public/v1/n8n/accounting. Their existing general event permissions remain separate. All three integrations use the same document and PDF reads. See Invoice accounting documents.

Upcoming release — Accounting export package

The asynchronous export catalog adds company-accounting-zip: invoice and invoice-line CSVs, VAT totals by billing profile/currency/rate, payment attempts, Chargebacks, interpretation warnings and original PDFs. Request an inclusive dateFrom/dateTo period with exports:write, then poll and download using exports:read. Existing export types and response fields remain available. See Accounting package. Make accounting connections can request platform:read, exports:read and exports:write through explicit company consent. Existing connections and token refreshes retain their approved permissions.

Upcoming release — Public API collection pagination

Public API v1 collection reads default to 10 records and clamp requests to 100 per page. Own company/client records remain pageable without an artificial page ceiling. Shared public workout catalogues stop at page ten. Tags and custom field definitions become always paginated. Existing record fields, collection keys and cursor formats are preserved. Compatible Make, Zapier and n8n consumers follow continuation metadata. This policy is prepared for release; it is not a deployment assertion. These changes apply only to /public/v1. Existing /api, /app/v1, nutrition catalogue and MCP behavior is preserved. See collection pagination transition.

2026-10-24

Optional pagination for client catalogs

GET /public/v1/client-tags and GET /public/v1/client-custom-fields accept page and limit for paginated reads, with standard pagination metadata and a maximum page size of 500. Omitting both parameters keeps the complete list response. Existing array keys, item fields and required scopes are unchanged. See Clients.

2026-10-23

Provider-scoped automation webhooks

The enabled Make integration supports company-consented OAuth connections and dedicated event subscriptions through /public/v1/oauth/make and /public/v1/make. The new make_webhooks:read and make_webhooks:write scopes require fresh consent. Existing grants are not expanded. Availability depends on the provider rollout and deployed backend version.

Client custom field editability

Client custom field definitions now include a readOnly boolean. Use it to exclude automatically managed or otherwise non-editable fields from update forms. See Client lifecycle.

2026-10-22

Subscription cancellation reasons in MCP (MCP 1.5.0)

list_subscriptions and get_subscription include cancellationRequest with the recorded cancellation reason, reason code and label, free-text explanation, additional message and request date. It is null when no cancellation information is available. Existing subscriptions module access applies; no new input fields or scopes are required. See Subscriptions.

Staff, locations, retention, registrations and notifications in MCP (MCP 1.4.0)

New read tools: list_staff, list_locations, list_retention_members, list_retention_approvals, list_client_field_catalog, list_registration_requests, list_membership_action_requests, list_notifications and get_notification. list_calendar_events and list_bookings accept an optional locationId filter. search_clients and get_client include the member’s tags and home location in relationship.tags and relationship.homeLocation. search_clients can filter by tag name and homeLocationId. get_retention_planner_rules returns the company’s retention planner rules, including conditions and configured actions. get_location_availability returns the configured availability windows per location, with open hours per day and per week. See Clients and Calendar events.

2026-10-21

Stored height in MCP goals (MCP 1.3.0)

get_client_goals and client_ai_get_my_goals include stored height in centimeters at goals.bodyInfo.heightCm when available. The value belongs to the client’s goals in the connected company and requires health data consent. See Goals and Client AI goals.

2026-10-20

Legacy workout overview retirement

The deprecated GET /public/v1/workout/plans/get/clients/{clientId}/workout endpoint returns HTTP 410 Gone. Use GET /public/v1/workout/plans/assigned for assigned plans or GET /public/v1/workout/performance/sessions/current for the current session. See the API Reference.

2026-10-19

Read-only Group Workout details

GET /public/v1/workout/groups/runs/{runId} and GET /public/v1/workout/groups/sessions/{sessionId} accept readOnly=true to retrieve recorded results without preparing or updating the session. The response shape and access requirements remain the same. See the API Reference.

Twelve-week membership billing

Membership catalog create and update operations accept Payment per 12 weeks for period. Each billing period spans 84 days; contract duration and credit allocation frequency remain separate settings. See Finance.

2026-10-15

Exercise search tracking type

  • GET /public/v1/workout/exercises/search and its /app/v1 counterpart now include items[].type, resolved from the catalog’s defaultType with a reps fallback. defaultType is retained; day-specific overrides remain in planPrescription.type. Catalog create/update also accept bodyweight, weighted_bodyweight, and assisted_bodyweight as default types. No migration is required. See the workout operations in the API Reference.

Nutrition recipes and safe MCP retries (MCP 1.2.2)

  • Nutrition MCP recipe writes preserve ingredient lines and scale macros by servings or weight. Historical recipe entries with stored totals contribute to recalculated daily totals. Invalid recipe replacements are rejected before removing the existing item. See Nutrition logs.
  • Query-budget and circuit rejections before mutation execution can retry the same arguments and idempotency key after retryAfterMs. Completed operations retain replay protection. See Troubleshooting.
  • Plan-item tool descriptions explicitly identify base-plan changes and direct date-specific edits to the day-item tool. See Nutrition plans.

Past weeks on the weekly ranking

  • GET /public/v1/workout/clients/{clientId}/weekly-ranking accepts weekStart to retrieve a past week’s leaderboard.
  • Responses include isCurrentWeek; past weeks return resetLabel: null.
See the workout operations in the API Reference.

2026-10-14

Booking-bound QR admission

  • Access QR codes can be bound to a product, booking occurrence, and location. Member QR responses include booking eligibility and UTC validity intervals.
  • Breaking retry behavior: each QR authorizes one scan. Replays return QR_ALREADY_USED; refresh the QR after an uncertain response. Badge scanId retries retain their existing idempotency.
  • Optional limits can restrict admission per booking.
See Access devices.

Hidden training plans

Training plans support a coach-managed visibleToClient flag. Plans with visibleToClient: false stay available to staff and are hidden from the client portal, mobile app, and client training MCP. See Client training tools.

2026-10-13

Client document folders and uploads (MCP 1.2.0)

  • Added POST /public/v1/clients/{clientId}/document-folders, POST /public/v1/clients/{clientId}/documents/uploads, and POST /public/v1/clients/{clientId}/documents/uploads/{uploadId}/complete.
  • Company MCP adds create_document_folder, link_client_document, prepare_client_document_upload, and complete_client_document_upload.
  • Upload PDF, TXT, DOCX, XLSX, JPEG, or PNG files up to 25 MiB. Flat folders are supported. Writes require documents:write, health consent, and an Idempotency-Key.
See Documents API and Document tools.

Operational client lifecycle updates

PATCH /public/v1/clients/{clientId}/lifecycle updates trial, active, paused, and inactive relationships, derives member status, and controls portal access. Requires clients:write. See Client lifecycle updates.

Central client sign-in for MCP connections

Clients can connect an AI assistant with their email and password, select a company, and approve access without knowing their portal address. The connection page explains unavailable companies. See Client AI access and Connection.

2026-10-12

External client access and durable references

  • Added app and client-AI access entitlements with finite paid intervals, revision ordering, and dedicated scopes. Company administrators opt OAuth clients into external relationship management.
  • Added durable references for clients, exercises, and workout plans, including exact client-reference lookup and versioned binding for existing clients.
See External client access and External references.

Structured MCP cardio prescriptions

upsert_workout_plan_activity accepts structured cardio prescriptions for the selected sport and control signal. Requires the cardio builder feature; pass null to remove a prescription. See Workout tools.

2026-10-09

Scheduled MCP workout activities

Added list_workout_plan_activities, upsert_workout_plan_activity, and remove_workout_plan_activity for running, cycling, swimming, and other scheduled activities. Reads support week filtering and pagination. See Workout tools.

2026-10-07

Public Workout API

  • Added /public/v1/workout operations for exercise libraries, company and client plans, multiweek programmes, calendars, sessions, groups, settings, and progress.
  • Granular scopes separate workout reads, writes, and progress access. Writes require an Idempotency-Key.
See API Reference.

Location expansion approval

Additional real branches require FITsociety admin approval. Creating or promoting one without approval returns 409 COMMERCIAL_EXPANSION_APPROVAL_REQUIRED. See Company catalog.

2026-09-30

Nutrition templates and assignment

Added create_nutrition_plan_template for reusable company templates and assign_nutrition_plan to copy a template into a client’s plan and date window. See MCP tools.

Workout scheduling and assignment

  • Workout templates support scheduleMode: "multi_week", numbered weeks, and weekday placement through upsert_workout_plan_day.
  • search_workout_exercises supports compact results. update_client_workout_plan_status activates or deactivates an assigned plan without changing its source template.
  • get_calendar_event includes occupancy, waiting-list, and capacity details. Pass startAt for a specific recurring occurrence.
See Workout tools and MCP tools.

2026-09-17

Nutrition templates and client notes

  • list_nutrition_plans accepts an omitted clientId to list company templates, or a client ID to list assigned plans.
  • Added get_client_note to retrieve a full accessible client note.
See Nutrition plans and MCP tools.

2026-09-15

Workout and WOD effort settings

Added rpeEnabled and showSetRpe to workout and WOD exercise contracts. RPE visibility and per-set input preferences can be configured independently.

2026-09-10

Localized Public API text

Breaking input change: localized authoring fields use language maps and defaultLanguage instead of plain strings. A supplied map replaces all translations; omitted PATCH fields retain their values. See Localized text.

Wishlist tools (MCP 1.1.0)

Added the opt-in company/coach wishlist module with search_wishlist, get_wishlist_item, submit_wishlist_request, and vote_wishlist_item. Submissions and votes require separate write grants. See Wishlist tools.

2026-09-09

MCP catalog and contracts (MCP 1.0.0)

  • Tool discovery includes an outputSchema for every company/coach and client tool. Optional ?catalog=all discovery exposes the fixed catalog.
  • Write tools accept idempotencyKey as an argument as well as request metadata. OAuth connections with mixed account scopes support account selection.
See Connection and Examples.

Public API client creation and recent records

  • Breaking response change: creating a client with an existing email links that account to the company and returns HTTP 200. An existing company link returns HTTP 409.
  • Client listing supports an exact case-insensitive email filter. Added GET /public/v1/clients/recent and GET /public/v1/bookings/recent.
See Clients.

Brand assets

Added downloadable logos, icons, a ZIP kit, and brand guidelines on the Brand assets page.

Form templates and client actions

  • Added form template creation, updates, and archive actions with forms:write.
  • Removed endpoint: POST /public/v1/clients/{clientId}/relationship/approve is no longer part of the Public API.

2026-08-26

Asynchronous Public API exports

  • Added /public/v1/exports for export type discovery, creation, status, downloads, cancellation, retries, and deletion. Uses exports:read and exports:write scopes.
  • XLSX export types also support CSV. Multi-sheet CSV exports return a ZIP with one file per worksheet. Completed exports provide temporary signed download URLs.
See Async exports.

2026-08-11

MCP agent setup

Added Agent Setup and a machine-readable setup prompt for connecting coding agents to FITsociety MCP.

2026-08-07

Decimal credit-pack validity

Credit-pack creditValidity.value accepts decimal values. Membership validity continues to use whole numbers.

2026-07-27

Default event locations

Event templates support a default location. Templates without an explicit location use the configured default.

2026-07-21

Calendar availability management

Added GET/PUT /public/v1/coaches/{coachId}/availability and GET/PUT /public/v1/locations/{locationId}/availability, with coach_availability:* and location_availability:* scopes.

Event types and templates

Added event type and template resources for creation, updates, and archiving at /public/v1/event-types and /public/v1/event-templates, replacing legacy lesson types.

OAuth replaces legacy company API keys

Breaking authentication change: Public API access uses OAuth client credentials. Legacy company API keys and the x-api-key header are no longer supported.

2026-07-18

Client AI nutrition tools

Added client MCP tools for logging and searching food products and recipes.

MCP server address

The MCP server moved to https://mcp.fitsociety.io/mcp/v1.

2026-07-14

Developer portal and outbound webhooks

  • Added the developer portal with Public API guides, API Reference, MCP documentation, and a changelog.
  • Added outbound webhook management and delivery routes under /public/v1/webhooks.