ClubWorx API

Name: ClubWorx API API
Brand: ClubWorx API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer16 EndpointsREST

For Agents

Run a ClubWorx-managed gym or studio programmatically — manage members, memberships, classes, bookings, payments, and facilities.

Connect the ClubWorx API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClubWorx API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ClubWorx API API.

Create, update, list, and delete member records

Create memberships and list active memberships across the club

Schedule classes and list the class timetable

Take and cancel bookings against scheduled classes

GET STARTED

Start building with ClubWorx API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ClubWorx API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ClubWorx API, keeping it validated and agent-ready. The ClubWorx API is the integration surface for the ClubWorx club and membership management platform used by gyms, martial arts schools, and fitness studios. It exposes endpoints for members, memberships, classes, bookings, payments, and facilities. Authentication uses a JWT Bearer token, and the 16 endpoints cover the day-to-day operational surface needed to run the front desk, take bookings, and process member payments.

Use Cases

Patterns agents use ClubWorx API API for, with concrete tasks.

★ Member Onboarding From a Studio Website

Martial arts schools and boutique gyms running their own signup landing page push the form data into ClubWorx via POST /members and create a membership through POST /memberships in the same flow. The endpoints accept the contact details and membership plan, return the created IDs, and the front desk staff see the new member in the dashboard within seconds. End-to-end this replaces manual entry at the desk and removes typos in member contact records.

When a website signup form is submitted, POST /members with the member's details, then POST /memberships with the returned member_id and the chosen plan

Class Booking Through a Member App

Clubs offering a branded member app drive class browsing and booking through GET /classes and POST /bookings. The class list returns scheduled sessions across all facilities, and the booking endpoint takes a member_id and class_id, returning a booking confirmation. DELETE /bookings/{booking_id} handles cancellations from the same app surface, keeping the ClubWorx schedule as the single source of truth for class capacity.

List next 7 days of classes via GET /classes, render them in the member app, and POST /bookings when the member selects a class

Membership Payment Recording From an External Processor

Studios that take payments through Stripe, Square, or a regional processor record the resulting payment back into ClubWorx via POST /payments so the membership ledger stays accurate. The membership ID, amount, and payment method ride on the request, and GET /payments lets finance pull a per-member payment history during reconciliation. This pattern keeps the operational truth in ClubWorx without forcing the studio to take card payments only through the in-app processor.

After a Stripe charge succeeds for a membership renewal, POST /payments to ClubWorx with the membership_id, amount, currency, and external transaction reference

AI Agent Running a Studio Front Desk via Jentic

AI agents handling phone or chat enquiries for a martial arts school or boutique gym call ClubWorx through Jentic to take new members, book classes, and answer schedule questions. The agent expresses an intent like 'book a member into a class', and Jentic loads the matching ClubWorx operation, supplies the JWT Bearer token from the vault, and returns the structured response so the agent can confirm the booking to the caller.

Through Jentic, search for 'book a member into a class', load the clubworx.com /bookings operation, and execute it with member_id and class_id

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for clubworx api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/members

List members

POST

/members

Create a member

POST

/memberships

Create a membership

GET

/classes

List classes

POST

/bookings

Create a booking

DELETE

/bookings/{booking_id}

Cancel a booking

POST

/payments

Record a payment

GET

/facilities

List facilities

GET

/members

List members

POST

/members

Create a member

POST

/memberships

Create a membership

GET

/classes

List classes

POST

/bookings

Create a booking

DELETE

/bookings/{booking_id}

Cancel a booking

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The ClubWorx JWT Bearer token is stored encrypted in the Jentic vault (MAXsystem) and applied to the Authorization header only at execution time. The agent never sees the raw token, and it is not written into prompt history.

Intent-based discovery

Agents search by intent (e.g. 'create a member', 'book a class', 'record a payment') and Jentic returns the matching ClubWorx operation with its input schema, so the agent can call /members, /bookings, or /payments without browsing app.clubworx.com/api/docs/v2.

Time to first call

Direct ClubWorx integration: a day to wire JWT auth, member create, booking create/cancel, and payment recording. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mindbody API

Mindbody covers a similar member, class, and booking workflow at a larger scale across fitness, wellness, and beauty

Choose Mindbody when the studio is on its larger ecosystem; choose ClubWorx for a lighter-weight studio management product

Alternative

Clubplanner API

Clubplanner is a directly comparable gym and fitness club management API with members, classes, and bookings

Choose whichever the club already uses; both APIs cover the same operational surface so the choice typically follows the existing platform contract

Complementary

Stripe API

Stripe processes the membership card payment that is then recorded back into ClubWorx via POST /payments

Use Stripe to charge the member's card, then call ClubWorx /payments with the resulting transaction reference to keep the ledger consistent

FAQs

Specific to using ClubWorx API API through Jentic.

Why is there no official OpenAPI spec for ClubWorx API?

ClubWorx does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ClubWorx API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ClubWorx API use?

The ClubWorx API uses an HTTP bearer scheme with a JWT Bearer token in the Authorization header. Tokens are issued from the ClubWorx admin panel. Through Jentic the token is stored encrypted in the vault and applied at execution time, so the agent never sees it.

Can I create members and memberships in one flow?

Yes. POST /members creates the member record, then POST /memberships ties a plan to that member's ID. Both endpoints return the created object so the front-end can immediately reflect the new state without polling.

Can I take and cancel class bookings with the ClubWorx API?

Yes. POST /bookings creates a booking for a member against a scheduled class, GET /bookings/{booking_id} retrieves it, and DELETE /bookings/{booking_id} cancels it. Cancellation is the standard way to free a class slot when a member can't attend.

What are the rate limits for the ClubWorx API?

The OpenAPI specification does not declare explicit rate limit headers or a 429 response. ClubWorx applies plan-level limits, and integrations should batch reads (e.g. one /classes call per day rather than per session) and back off on transient failures. Through Jentic, retries are handled by the SDK.

How do I record a payment in ClubWorx through Jentic?

Install the SDK with pip install jentic, search for 'record a payment', load the clubworx.com /payments operation, and execute it with the membership_id, amount, and payment method. Jentic supplies the JWT Bearer token automatically and returns the recorded payment.

Can I list facilities available for a class?

Yes. GET /facilities returns the list of rooms, courts, or mats configured on the account so a scheduling integration can pick the correct facility when creating a class via POST /classes.