Exercise.com
Exercise.com gym and coaching software: members and staff, appointments and classes, scheduled occurrences and rosters, visits and check-ins, calendar, services, locations, availability schedules, waitlists, assessments, groups and logged workouts. Tenant API v4 on your own platform host.
7 æ¥éç¡æ · ã¯ã¬ãžããã«ãŒãäžèŠ Â· EU ãã¹ã
Exercise.com ã«äœã§ãèãã
AnythingMCP çµç±ã§ Exercise.com ã«å®éã®ããã³ããã詊ãã â Claude ãããŒã«ãåŒã³åºããåçããŸããããªãã®ã¡ãã»ãŒãžã§ Enter ãæŒããš Cloud ã«ã€ã³ã¹ããŒã«ããŸãã
Exercise.com ã Cloud ã«ã€ã³ã¹ããŒã«Claude 㯠AI ã®ãã誀ãããšããããŸããåçãã確èªãã ããã
2 åã§ã»ããã¢ãã
- 1cloud.anythingmcp.com ã§ç¡æãã©ã€ã¢ã«éå§ã
- 2ã³ãã¯ã¿ãŒã¹ãã¢ã§ Exercise.com ãã¯ãªãã¯ãè³æ Œæ å ±ã貌ãä»ãã
- 3MCP API ããŒãçºè¡ããAI ã¯ã©ã€ã¢ã³ãã MCP URL ã«åããã
Exercise.com ã®ã¬ã€ã
äž»èŠ AI ã¯ã©ã€ã¢ã³ãåãã®ã¹ããããã€ã¹ãããã»ããã¢ããã
Exercise.com ã®ã»ããã¢ãã
ã³ãã¯ã¿å®çŸ©ãã®ãã®ããïŒèªèšŒæ å ±ã®å ¥æå ãå¿ èŠãªæš©éããã®ã¢ããã¿ãåŒã³åºã APIã ã³ãã¯ã¿äœè ã«ããè±èªã§æäŸãããŠããŸãã
Credentials: Exercise.com runs each business on its own host (your custom-branded platform, e.g. train.yourgym.com or yourgym.exercise.com). Put that host, without https://, in EXERCISE_HOST; the API is served from it at /api/v4.
API access is a paid add-on: ask your Exercise.com account representative to enable it. The v4 API takes two credentials on each call, as its reference documents (security api_key and bearer together):
EXERCISE_API_KEY: create it under Account > Customize Platform > Developers > Add and copy it at once (it is shown only once). Sent in theAPI-TOKENheader.EXERCISE_ACCESS_TOKEN: the bearer token of the account the API acts as (a Personal API Token issued in the product, or the token provided with API access), sent asAuthorization: Bearer. Use a token of the owner or an admin to see every member. Most member, booking and service reads answer with the access token alone, but schedules, assessment templates and logged workouts answer 401 unless both are sent.
Where to start: exercise_com_list_users gives member and staff ids (user_id). For bookings use exercise_com_get_calendar with affinity=schedule and a Unix-time window, or exercise_com_list_appointments / exercise_com_list_scheduled_appointments, then exercise_com_list_visits with appointment_id for who booked and attended.
Filtering: most list tools take filter, Ransack predicates written as a query-string fragment: q[status_eq]=completed&q[created_at_gteq]=2026-09-01. Keys are <field>_<predicate> such as _eq, _in, _gteq, _lteq, _cont; q[s]=created_at desc sorts. Unknown fields are ignored or rejected depending on the resource, so start without a filter and look at the field names in the answer.
Appointments need a date window: exercise_com_list_appointments over the whole history is slow enough to fail with HTTP 500, so its filter is required; pass q[start_time_gteq] and q[start_time_lt].
Paging: per and page (from 1). When either is set, the answer includes meta.total. Without them some lists return everything. pluck_columns returns a plain array of just those stored columns for every match (it can ignore per), handy for id lookups; computed fields such as service_name are not columns and make the call fail.
Times: the calendar takes Unix timestamps in seconds for start and end; other filters take dates or ISO 8601 times. Visits carry the time zone of the business.
Errors: 401 Access denied means a wrong host, a wrong or revoked token, or API access not enabled; 403 means the token's account may not see the resource; 404 a wrong id.
The interactive reference is at https://train.demoexercise.com/api-docs/ ("API V4 Docs"); its login is given in Exercise.com's support article on API keys (the docsUrl of this connector).
Packages, user packages, invoices and charges are not part of the documented v4 tenant API; Exercise.com documents them only in its newer API at api.exercise.com.
ããªãã® AI 㯠Exercise.com ãã 2 ã¯ãªãã¯å ã
ã³ãã¯ã¿ãŒãã€ã³ã¹ããŒã«ãè³æ Œæ å ±ã貌ãä»ããAI ã«è³ªåã7 æ¥éç¡æãã¯ã¬ãžããã«ãŒãäžèŠã