Clubplanner API

Name: Clubplanner API API
Brand: Clubplanner API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbasic12 EndpointsREST

For Agents

Manage gym and fitness club operations programmatically — create and update members, schedule and list classes, take and cancel class bookings, and read membership records.

Quickstart

Get started with Clubplanner API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"book a member into a fitness class"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Clubplanner API API.

Create, update, list, and delete gym member records

Create and list group fitness classes on the schedule

Take member bookings against classes and cancel them when needed

Look up an individual member or class by ID for confirmation flows

Read existing membership records associated with members

GET STARTED

Start building with Clubplanner API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Clubplanner API, keeping it validated and agent-ready. The Clubplanner API is the integration surface for the Clubplanner gym and fitness club management platform. It exposes endpoints to manage members, group fitness classes, bookings, and membership records. Authentication uses HTTP Basic with credentials issued from the Clubplanner admin panel, and the API is sized for typical club operations with 12 endpoints covering create, read, update, and delete on the core entities.

Use Cases

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

★ Member Sign-Up From a Club Website

Gyms running their own website or signup landing page send the form data straight into Clubplanner via POST /members rather than re-keying it in the admin UI. The endpoint accepts the member fields, returns the created record's ID, and that ID is then used for /memberships lookups and future bookings. End-to-end signup feels instant to the prospect and removes the data-entry step that creates errors in member contact details.

When a website signup form is submitted, POST /members with the member's name, email, phone, and date of birth and store the returned member ID in the form vendor's record

Class Schedule and Booking Synchronisation

Clubs that publish their schedule in a custom mobile app or a partner platform read class data from GET /classes and accept member bookings via POST /bookings. The same flow drives in-club kiosks where members book themselves into the next class without staff involvement. DELETE /bookings/{id} handles cancellations from the same surface, keeping Clubplanner as the single source of truth.

Pull next 7 days of classes via GET /classes, render them in a member app, then POST /bookings with the member ID and class ID when the member taps Book

Membership Audit and Cleanup Jobs

Operations managers run scheduled jobs against the Clubplanner API to audit membership data — flagging members whose memberships have expired, identifying duplicates, and removing test records. GET /members and GET /memberships provide the data, and DELETE /members/{id} removes records flagged for deletion at the end of legal retention. This pattern keeps the database clean without reaching into the underlying tables.

List all members via GET /members, list memberships via GET /memberships, identify members whose membership has expired more than 12 months ago, and delete those records via DELETE /members/{id}

AI Agent Running a Front Desk via Jentic

AI agents running customer service for a gym chain can call Clubplanner through Jentic to take new members, book existing members into classes, or handle cancellations. The agent expresses an intent like 'book a member into a class', and Jentic loads the matching Clubplanner operation, supplies the Basic Auth credentials from the vault, and returns the structured booking response. The agent can confirm the booking to the caller without reading clubplanner.com/api/docs.

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

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/members

List members

POST

/members

Create a member

PUT

/members/{id}

Update a member

GET

/classes

List classes

POST

/classes

Create a class

GET

/bookings

List bookings

POST

/bookings

Create a booking

DELETE

/bookings/{id}

Cancel a booking

GET

/members

List members

POST

/members

Create a member

PUT

/members/{id}

Update a member

GET

/classes

List classes

POST

/classes

Create a class

GET

/bookings

List bookings

Why though Jentic?

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

Credential isolation

The Clubplanner Basic Auth username and password are stored encrypted in the Jentic vault (MAXsystem) and combined into the Authorization header only at execution time. The agent never sees the raw credentials, and they are not written into prompt history.

Intent-based discovery

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

Time to first call

Direct Clubplanner integration: half a day to a day to wire up Basic Auth, member create/update, and booking flows. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mindbody API

Mindbody is a larger fitness, wellness, and beauty platform with a comparable member, class, and booking API

Choose Mindbody for studios already on its platform; choose Clubplanner when the requirement is the lighter-weight Clubplanner gym management product

Alternative

Clubworx API

Clubworx is a directly comparable gym management platform with members, classes, and attendance tracking

Choose Clubworx for clubs already on its platform; the two APIs cover similar operations and the choice typically follows the existing club management contract

Complementary

Calendly API

Calendly handles personal training and consultation scheduling that pairs with Clubplanner group classes

Use Calendly to book 1-on-1 PT sessions and Clubplanner /bookings for group fitness classes in the same membership

FAQs

Specific to using Clubplanner API API through Jentic.

Why is there no official OpenAPI spec for Clubplanner API?

Clubplanner does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clubplanner 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 Clubplanner API use?

The Clubplanner API uses HTTP Basic authentication: a username and password issued from the Clubplanner admin panel are encoded into the Authorization header on every request. Through Jentic the credentials are stored encrypted in the vault and applied at execution time, so the agent never sees them.

Can I create a new gym member with the Clubplanner API?

Yes. POST /members accepts the member's name, contact details, and date of birth, and returns the created record's ID. The same record can then be retrieved with GET /members/{id} or updated with PUT /members/{id}.

Can I take class bookings through the Clubplanner API?

Yes. POST /bookings creates a booking for a member against a scheduled class, and DELETE /bookings/{id} cancels it. GET /bookings lists the bookings on the account so you can present a member's upcoming classes.

What are the rate limits for the Clubplanner API?

The OpenAPI specification does not declare explicit rate limit headers or a 429 response. Clubplanner applies plan-based limits, and integrations should batch member and booking lookups rather than calling once per record. Through Jentic, retries are handled by the SDK.

How do I book a member into a class with the Clubplanner API through Jentic?

Install the SDK with pip install jentic, search for 'book a member into a class', load the clubplanner.com /bookings operation, and execute it with the member_id and class_id. Jentic supplies the Basic Auth credentials automatically and returns the created booking.