Health & fitness
Mindbody
Classes, rosters, clients, visits and contracts for your studio.
13 endpoints
Hapana sells a read-only API on Premium and a read and write API on Pro, and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted Hapana MCP server with 31 tools that ChatGPT and Claude use in your own CORE login. Charges, membership changes and member messages wait for your OK.
31 tools Read and write
Hapana has an API, tied to its plans. Premium includes read-only API access with self-service keys and read webhooks. Pro includes full read and write APIs with self-service keys, all webhooks and metered premium actions. No Hapana MCP server and no official ChatGPT or Claude connector was found.
| What you need | Hapana API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server | Copy and paste | Hosted MCP server |
| Change memberships, bookings and charges | Pro plan, your own code | One screen at a time | 31 tools, writes after your OK |
| Read clients, schedule and reports | Premium or Pro | One screen at a time | Any plan, your login |
| Run from n8n or a script | With your own client | Manual only | REST, same key |
Checked 15 Nov 2026. Sources: Hapana pricing · Hapana API connectors · KB: Set Up and Manage Your Integrations · KB: Create Memberships and Packages · KB: Schedule templates · KB: Add a New Session · KB: Session Types · KB: Add a New Client · KB: Process a New Sale · KB: Process a Refund · KB: Suspend a Membership · KB: Cancel a Membership · KB: Reactivate a Membership · KB: Bulk messages · KB: Email campaign in GROW · KB: Bulk SMS in GROW · KB: No Show Fee · KB: Check In a Client · KB: Book a Group Exercise Class · KB: Promo Codes · KB: POS Products · KB: Retail and Gift Card Sales · KB: Merge Duplicate Clients · KB: Client Groups · KB: Leads · KB: Workout Programs · KB: Substitute an Instructor · KB: Bulk Cancel Sessions · KB: Pending Payment · KB: Add Credits to a Package · KB: Extend Package Credit Validity · KB: Package Agreement Signature · KB: Manual Time Clock Entry · KB: Create a Free Class · KB: Rooms as Bookable Resources · KB: Re-send an Invoice · KB: Waitlist · KB: Payroll Report · KB: Delinquency Report · KB: Export Contacts · KB: Import Contacts · KB: Bulk Edits to Memberships
Once, in a browser we host for you.
One address in its settings.
It lists the change, you approve it.
Your agent works in your own signed-in Cloud Browser. Charges, refunds, membership changes and member messages wait for your OK. Who can see your session
Sign in to Hapana in a Cloud Browser. Open core.hapana.com/login in your Cotlet Cloud Browser and sign in with your own CORE login. Add GROW in the same browser if you use it.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Hapana sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Hapana on after connecting? Refresh the connector and the 31 Hapana tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: hapana_read One tool per workflow in the Hapana Knowledge Base, across CORE and GROW. The three read tools run at once; every write asks first.
Start with find_client: most tools take the client it returns. Groups are reused for messages and class bookings.
The same search the Clients tab offers. Returns the profile with its memberships and packages, their status and the payment schedule. Most other tools take the client it returns. It changes nothing.
MCP callhapana_read → find_client
REST endpointGET https://cotlet.dev/api/v1/hapana/clients/find
| Name | Type | Description |
|---|---|---|
| query string required | string | Name, email address or phone number. |
{
"query": "query"
} {
"client": "Example Member",
"email": "member@example.com",
"memberships": [
{
"name": "Unlimited Monthly",
"status": "Active",
"next_payment": "2026-11-20"
}
],
"packages": [
{
"name": "10 Class Pack",
"credits": 3,
"expires": "2026-12-01"
}
]
} The client can then buy a membership and book. A welcome email reaches the client, so the agent shows you the details first. Search with find_client before adding, so nobody is added twice. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → add_client
REST endpointPOST https://cotlet.dev/api/v1/hapana/clients
| Name | Type | Description |
|---|---|---|
| fields object required | object | The sign-up fields your account requires (Account Settings, Configuration): name, email, phone and the rest. |
| send_welcome_email boolean | boolean | Send the client a login link. Default false. |
{
"fields": "fields"
} {
"client": "New Member",
"email": "new.member@example.com",
"welcome_email": true,
"saved": true
} Contact details, visit history and remaining credits move into the kept profile. Hapana requires active memberships and packs on the duplicate to be cancelled first; the agent checks and stops if they are not. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → merge_clients
REST endpointPOST https://cotlet.dev/api/v1/hapana/clients/merge
| Name | Type | Description |
|---|---|---|
| from_client string required | string | The duplicate to merge from. |
| into_client string required | string | The profile to keep. |
{
"from_client": "from client",
"into_client": "into client"
} {
"from_client": "Example Member (duplicate)",
"into_client": "Example Member",
"merged": true
} Groups are reusable for messages (send_bulk_message) and for booking a whole group into a class (book_client). The list shows each group's member count. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → manage_client_groups
REST endpointPOST https://cotlet.dev/api/v1/hapana/client-groups/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `add_clients`. `list` only reads. |
| group string | string | Group name, for example 6 Week Challenge. |
| clients array | array | Clients to add, by name, email or phone. |
{
"action": "action"
} {
"group": "6 Week Challenge",
"members": 18,
"saved": true
} Works in the Leads tab of Clients in CORE. Assigning gives each team member a clear list of who to follow up. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → manage_leads
REST endpointPOST https://cotlet.dev/api/v1/hapana/leads/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `assign`, `update`, `delete`. `list` only reads. |
| lead string | string | Lead name, for every action but `add` and `list`. |
| fields object | object | Name, email, phone and lead source (walk-in, referral, Instagram). |
| assign_to string | string | Team member, for `assign`. |
{
"action": "action"
} {
"lead": "Example Prospect",
"source": "Instagram",
"assigned_to": "Front desk",
"saved": true
} The Client Program Log shows each sent program as Pending, Active or Done, and clients can track progress and leave notes on it. Sending reaches the client, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → send_workout_program
REST endpointPOST https://cotlet.dev/api/v1/hapana/workout-programs
| Name | Type | Description |
|---|---|---|
| name string required | string | Program name, for example 6-Week Strength Challenge. |
| sections object | object | Warm-up, workout and cool-down: per exercise its type, name, equipment, reps, sets, rest and resistance. |
| send_to string | string | A client or a client group. |
{
"name": "Jane Doe"
} {
"program": "6-Week Strength Challenge",
"sent_to": "6 Week Challenge",
"status": "Pending"
} Suspend, cancel or bring back a membership, top up or extend a pack, change future rates and send agreements to sign.
A suspension pauses billing and access for its dates. A dated cancellation runs between 00:00 and 4:00 on that date. `active` resumes a suspension and `remove_cancellation` removes a scheduled one, so the client keeps the membership instead of buying a new one. Each change affects what the client pays. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → update_membership_status
REST endpointPATCH https://cotlet.dev/api/v1/hapana/membership-status
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, email or phone, as find_client returns it. |
| membership string required | string | Membership or package name on the client's profile. |
| status string required | string | One of `suspended`, `cancelled`, `active`, `remove_cancellation`. |
| start_date string | string | ISO date it takes effect. Empty means immediately. |
| end_date string | string | For `suspended`: ISO date it ends. Empty means until resumed. |
| reason string | string | For `cancelled`: a cancellation reason from your list. |
{
"client": "Example Member",
"membership": "Unlimited Monthly",
"status": "suspended",
"start_date": "2026-11-20",
"end_date": "2026-12-20"
} {
"client": "Example Member",
"membership": "Unlimited Monthly",
"status": "suspended",
"start_date": "2026-11-20",
"end_date": "2026-12-20"
} Changes apply at once and show in the package history, and the client can book with the new balance. Useful for make-goods, bonus sessions and clients back from injury or travel. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → update_package_credits
REST endpointPATCH https://cotlet.dev/api/v1/hapana/package-credits
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, email or phone, as find_client returns it. |
| membership string required | string | Membership or package name on the client's profile. |
| credits integer | integer | Credits to add; negative to deduct. |
| valid_until string | string | New credit expiry, ISO date. Packages only, not memberships. |
{
"client": "client",
"membership": "membership"
} {
"client": "Example Member",
"package": "10 Class Pack",
"credits_before": 3,
"credits_after": 5,
"valid_until": "2027-01-15"
} Uses Bulk Edit Future Transactions in the Retail Dashboard, or a single client's membership. The agent lists every matching transaction and its current rate before it saves, because members will be charged the new rate. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → edit_future_payments
REST endpointPATCH https://cotlet.dev/api/v1/hapana/future-payments
| Name | Type | Description |
|---|---|---|
| client string | string | One client. Leave empty for a bulk edit. |
| memberships array | array | For a bulk edit: memberships, or a client group. |
| from string required | string | ISO date, first payment to change. |
| to string required | string | ISO date, last payment to change. |
| new_rate number required | number | New payment amount. |
{
"from": "from",
"to": "to",
"new_rate": 1
} {
"transactions": 42,
"from": "2026-12-01",
"to": "2026-12-31",
"old_rate": 49,
"new_rate": 54,
"saved": true
} The package must have Package Agreement switched on with its text in Retail Configurations, and the client needs a mobile number or email on file. The link reaches the client, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → send_package_agreement
REST endpointPOST https://cotlet.dev/api/v1/hapana/package-agreements
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, email or phone, as find_client returns it. |
| membership string required | string | Membership or package name on the client's profile. |
{
"client": "client",
"membership": "membership"
} {
"client": "Example Member",
"package": "Unlimited Monthly",
"agreement_sent_to": "member@example.com"
} Every tool here moves money. Refunds go back to the original payment method.
The New Sale screen of Payments. A sale charges the client, so the agent shows the cart, client and method before it pays. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → process_sale
REST endpointPOST https://cotlet.dev/api/v1/hapana/sale/process
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, email or phone, as find_client returns it. |
| item_type string required | string | One of `single_payment`, `recurring_payment`, `session_package`, `membership`, `product`, `gift_card`. |
| item string | string | The configured item, or for `single_payment` a description and price. |
| discount number | number | Discount on the item. |
| payment_method string | string | Account credit, or the card on file through Pay Securely. |
| gift_card object | object | For `gift_card`: design, to and from names, purchaser and recipient email, message, delivery date. |
{
"client": "client",
"item_type": "item type"
} {
"client": "Example Member",
"item": "10 Class Pack",
"total": 180,
"payment_method": "card on file",
"paid": true
} Refunds go to the original payment method, as Hapana recommends, never to cash or account credit unless you say so. `collect` charges a pending payment from the Payment Schedule so the membership stays active. Both move money. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → membership_payment
REST endpointPOST https://cotlet.dev/api/v1/hapana/payment/membership
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, email or phone, as find_client returns it. |
| membership string required | string | Membership or package name on the client's profile. |
| action string required | string | One of `refund`, `collect`. |
| amount number | number | For `refund`: full or partial amount, as your gateway allows. |
| payment_date string | string | ISO date of the payment. |
{
"client": "client",
"membership": "membership",
"action": "action"
} {
"client": "Example Member",
"membership": "Unlimited Monthly",
"action": "refund",
"amount": 49,
"method": "original card",
"done": true
} Available once the class is complete, for booked clients not marked attending; the fee comes from your Retail Settings. The agent lists the eligible clients and the fee before it charges. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → charge_no_show_fee
REST endpointPOST https://cotlet.dev/api/v1/hapana/no-show-fee/charge
| Name | Type | Description |
|---|---|---|
| session string required | string | Session name and start, as list_sessions returns it. |
| clients array | array | Clients to charge. Empty means every eligible no-show. |
{
"session": "session"
} {
"session": "Kickboxing, 2026-11-14 18:00",
"charged": [
"Example Member"
],
"fee": 15
} Uses Send Invoice Email in the Payments section of the client profile. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → send_invoice_email
REST endpointPOST https://cotlet.dev/api/v1/hapana/invoice-emails
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, email or phone, as find_client returns it. |
| invoice string required | string | Invoice date or number from the client's payments. |
| email string | string | Send to another address. Default the client's email. |
{
"client": "client",
"invoice": "invoice"
} {
"client": "Example Member",
"invoice": "2026-11-01",
"sent_to": "member@example.com"
} Read the day, add classes, book members or a whole group, check people in, cover instructors and cancel in bulk.
Reads the Schedule tab. Returns each session with its booked clients, capacity and waitlist. It changes nothing.
MCP callhapana_read → list_sessions
REST endpointGET https://cotlet.dev/api/v1/hapana/sessions
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO date. |
| to string | string | ISO date. Default: same day. |
| name string | string | Filter by class name. |
{
"from": "from"
} {
"sessions": [
{
"session": "Reformer Flow, 2026-11-16 07:00",
"instructor": "Instructor A",
"booked": 12,
"capacity": 12,
"waitlist": 2
},
{
"session": "Kickboxing, 2026-11-16 18:00",
"instructor": "Instructor B",
"booked": 9,
"capacity": 16,
"waitlist": 0
}
]
} Hapana advises setting up each weekday separately so later edits do not change other days by accident; the agent creates one session series per day. Clients can book once it is on the schedule. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → add_session
REST endpointPOST https://cotlet.dev/api/v1/hapana/sessions
| Name | Type | Description |
|---|---|---|
| template string required | string | Schedule template, for example Yoga Flow. |
| start string required | string | ISO date and time of the first session. |
| days array | array | Weekdays it recurs on. |
| end_date string | string | Last date. Empty for ongoing. |
| instructors array required | array | One or more instructors. |
| free boolean | boolean | Credit Required 0, Drop-in Price 0.00, Payment Required No. |
{
"template": "template",
"start": "start",
"instructors": "instructors"
} {
"template": "Yoga Flow",
"start": "2026-11-17T07:00",
"days": [
"Monday"
],
"instructors": [
"Instructor A"
],
"free": false,
"saved": true
} For members who call in or ask at the desk. When the class is full and its template has a waitlist, the client joins the waitlist and moves in automatically, in order, when someone cancels. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → book_client
REST endpointPOST https://cotlet.dev/api/v1/hapana/clients/book-client
| Name | Type | Description |
|---|---|---|
| session string required | string | Session name and start, as list_sessions returns it. |
| client string | string | A client. |
| group string | string | Or a client group. |
{
"session": "session"
} {
"session": "Reformer Flow, 2026-11-16 07:00",
"client": "Example Member",
"result": "waitlisted",
"position": 3
} Attendance shows in reports and applies the session credit. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → check_in_client
REST endpointPOST https://cotlet.dev/api/v1/hapana/client/check
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, email or phone, as find_client returns it. |
| session string required | string | Session name and start, as list_sessions returns it. |
{
"client": "client",
"session": "session"
} {
"client": "Example Member",
"session": "Kickboxing, 2026-11-14 18:00",
"attended": true
} Substitutes are recorded separately in payroll, so pick `substitute` when the regular instructor is only away. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → change_instructor
REST endpointPATCH https://cotlet.dev/api/v1/hapana/instructor
| Name | Type | Description |
|---|---|---|
| session string required | string | Session name and start, as list_sessions returns it. |
| instructor string required | string | A team member. |
| as string required | string | `substitute` for a one-off, `instructor` for a permanent change. |
{
"session": "session",
"instructor": "instructor",
"as": "as"
} {
"session": "Kickboxing, 2026-11-21 18:00",
"instructor": "Instructor C",
"as": "substitute",
"saved": true
} Hapana has no undo for this, so the agent lists every session it will cancel and waits. It saves the CSV record Hapana downloads. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → bulk_cancel_sessions
REST endpointPOST https://cotlet.dev/api/v1/hapana/cancel-sessions/bulk
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO date. |
| to string required | string | ISO date. |
| keep array | array | Sessions to leave on the schedule. |
{
"from": "from",
"to": "to"
} {
"from": "2026-12-24",
"to": "2026-12-26",
"cancelled": 11,
"kept": 1,
"csv": "cancelled-sessions.csv"
} Templates and session types, rooms, the memberships and packs you sell, promo codes and POS products.
Session types link classes to the memberships and packs that may book them. A deleted template cannot be scheduled again. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → manage_schedule_templates
REST endpointPOST https://cotlet.dev/api/v1/hapana/schedule-templates/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `delete`. `list` only reads. |
| template string | string | Template name, for example Boxing. |
| session_type string | string | Session type; a new one is created with a colour. |
| fields object | object | Description, duration, credits, payment and attendance settings, waitlist limit. |
| apply_to_future_sessions boolean | boolean | For `update`: also change every future session from it. |
{
"action": "action"
} {
"template": "Boxing",
"session_type": "Boxing",
"duration_minutes": 45,
"saved": true
} A room with no times set does not show on the scheduler and cannot be booked. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → configure_room
REST endpointPOST https://cotlet.dev/api/v1/hapana/room/configure
| Name | Type | Description |
|---|---|---|
| room string required | string | Room name, for example Cycle Studio. |
| availability array | array | Days and times the room appears on the schedule. |
| bookable boolean | boolean | Assign Room Resource Booking, for spot allocation. |
| allow_overlap boolean | boolean | Allow overlapping sessions. |
{
"room": "room"
} {
"room": "Cycle Studio",
"bookable": true,
"allow_overlap": false,
"saved": true
} Retail Configurations in Payments. A new offer with online purchase on appears in your app and on your website, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → manage_memberships_packages
REST endpointPOST https://cotlet.dev/api/v1/hapana/memberships-packages/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` only reads. |
| type string | string | `membership` or `package`. |
| name string | string | Shown in the app and widgets. |
| fields object | object | Description, categories, billing cycle and length, price, credits, session types, Enable Client Purchase Online. |
{
"action": "action"
} {
"type": "package",
"name": "Intro 3 Class Pass",
"price": 39,
"credits": 3,
"online": true,
"saved": true
} An active code discounts real sales, so the agent shows the discount and limits before saving. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → manage_promo_codes
REST endpointPOST https://cotlet.dev/api/v1/hapana/promo-codes/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` only reads. |
| name string | string | Promo name. |
| code string | string | What clients type, for example HALFPRICE. |
| discount object | object | Percentage or dollar amount, value, and the packages or memberships it applies to. |
| limits object | object | Start date, optional end date and total usage limit. |
{
"action": "action"
} {
"name": "January intro",
"code": "NEWYEAR20",
"discount": "20%",
"applies_to": "Packages",
"ends": "2027-01-31",
"saved": true
} Products need a POS category; a variable takes a barcode or a SKU, not both. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → manage_pos_products
REST endpointPOST https://cotlet.dev/api/v1/hapana/pos-products/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `remove`. `list` only reads. |
| product string | string | Product name. |
| variables array | array | Per size or colour: name, price, tax setting, barcode or SKU (one of them), track stock, stock count, online purchase. |
{
"action": "action"
} {
"product": "Studio T-shirt",
"variables": [
{
"name": "White Small",
"price": 35,
"stock": 12
}
],
"saved": true
} Bulk email, SMS and push from CORE; campaigns, SMS and contact files in GROW.
SMS uses your SMS credits. A message reaches every recipient at once, so the agent shows the audience size and text first. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → send_bulk_message
REST endpointPOST https://cotlet.dev/api/v1/hapana/bulk-messages
| Name | Type | Description |
|---|---|---|
| to string required | string | Clients, a group, or the booked or waitlisted clients of a session. |
| channel string required | string | `email`, `sms` or `push`. |
| message string required | string | The message. |
{
"to": "to",
"channel": "channel",
"message": "message"
} {
"to": "6 Week Challenge",
"channel": "push",
"recipients": 18,
"sent": true
} Needs a verified sending domain in your location. The agent shows recipients, subject and send time before it schedules. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → send_email_campaign
REST endpointPOST https://cotlet.dev/api/v1/hapana/email-campaigns
| Name | Type | Description |
|---|---|---|
| template string required | string | Saved email template. |
| recipients string required | string | Smart List, tags or selected contacts. |
| subject string | string | Default from the template. |
| send_at string | string | ISO date and time; empty sends now. |
{
"template": "template",
"recipients": "recipients"
} {
"campaign": "December timetable",
"recipients": 640,
"send_at": "2026-11-28T09:00",
"scheduled": true
} Needs an SMS number on the location, enough SMS credits and contacts opted in to SMS. The agent selects every matching record, not only the 20 on the first page. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → send_bulk_sms
REST endpointPOST https://cotlet.dev/api/v1/hapana/bulk-sms
| Name | Type | Description |
|---|---|---|
| contacts string required | string | Smart List or filter. |
| message string required | string | Text with custom values, for example the first name. |
{
"contacts": "contacts",
"message": "message"
} {
"contacts": "Lapsed 60 days",
"recipients": 85,
"sent": true
} An import can also bring Opportunities. Exports include the custom fields you choose. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → import_export_contacts
REST endpointPOST https://cotlet.dev/api/v1/hapana/export-contacts
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `export`, `import`. `export` only reads. |
| filter string | string | For `export`: Smart List, tag or date added. |
| file_url string | string | For `import`: a .csv under 30 MB, one tab, headers in row one. |
| mode string | string | For `import`: `add_new` or `update_existing`; empty values never overwrite. |
{
"action": "action"
} {
"action": "export",
"filter": "Tag: trial",
"contacts": 37,
"file": "contacts.csv"
} Missed shifts on the time clock, then the payroll and member delinquency reports.
Needs an Admin or Manager login. Entries feed the payroll report, so times are checked with you before saving. By default you confirm each call; you can switch that off for this tool.
MCP callhapana_write → add_time_clock_entry
REST endpointPOST https://cotlet.dev/api/v1/hapana/time-clock-entries
| Name | Type | Description |
|---|---|---|
| team_member string required | string | Staff member. |
| date string required | string | ISO date. |
| start string required | string | Start time. |
| end string required | string | End time. |
| notes string | string | Internal note. |
{
"team_member": "team member",
"date": "date",
"start": "start",
"end": "end"
} {
"team_member": "Front desk A",
"date": "2026-11-13",
"start": "09:00",
"end": "13:00",
"saved": true
} Payroll returns per team member the session count, hours from sessions and time clock, and earnings by rate. Delinquency by member returns each member once with oldest unpaid invoice age, past-due balance and payment method. It changes nothing.
MCP callhapana_read → get_report
REST endpointGET https://cotlet.dev/api/v1/hapana/report
| Name | Type | Description |
|---|---|---|
| report string required | string | One of `payroll`, `delinquency_by_member`, `delinquency_invoice_summary`, `delinquency_invoice_detailed`. |
| from string | string | Payroll: ISO date. |
| to string | string | Payroll: ISO date. |
| team_member string | string | Payroll: one staff member, empty for all. |
{
"report": "report"
} {
"report": "delinquency_by_member",
"members": [
{
"member": "Example Member",
"delinquency_age_days": 34,
"invoices": 2,
"past_due": 98
},
{
"member": "Sample Member",
"delinquency_age_days": 12,
"invoices": 1,
"past_due": 49
}
]
} Your signed-in Hapana browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 31 Hapana tools. The session cookie stays in the Cloud Browser.
The clients, schedule and payments your CORE role can open, and nothing more.
Team members and roles, payment gateway and payout settings, API keys, integrations and the kiosk.
You sign in again yourself, in the same Cloud Browser.
Disable Hapana for agents, reset the browser, or log out from all devices in Hapana.
Cotlet never sees or stores your password: you type it into Hapana yourself, and the agent only uses the session that login leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the Hapana server when CORE or GROW changes a screen, so your agent keeps working without a change on your side.
Some tools depend on what your account has switched on: a waitlist limit in the template, a no-show fee in Retail Settings, package agreements, an SMS number and credits in GROW. The agent works with your setup as it is.
If Hapana signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Action | How to put it right |
|---|---|
| Suspension or scheduled cancellation | update_membership_status with active or remove_cancellation |
| Package credits or expiry | Call update_package_credits again with the earlier numbers |
| Fee or sale charged | Refund it with membership_payment to the original method |
| Bulk cancelled sessions | No undo in Hapana: add them back with add_session |
| Message or campaign sent | Already with members: send a correction |
All 28 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 3 read tools, clients, the schedule and reports, run at once.
{
"name": "update_membership_status",
"arguments": {
"client": "Example Member",
"membership": "Unlimited Monthly",
"status": "suspended",
"start_date": "2026-11-20",
"end_date": "2026-12-20"
}
} curl -X PATCH https://cotlet.dev/api/v1/hapana/membership-status \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"client":"Example Member","membership":"Unlimited Monthly","status":"suspended","start_date":"2026-11-20","end_date":"2026-12-20"}' {
"client": "Example Member",
"membership": "Unlimited Monthly",
"status": "suspended",
"start_date": "2026-11-20",
"end_date": "2026-12-20"
} The example pauses a membership for a month instead of cancelling it, so the member comes back without buying a new one. A cron job or n8n flow can make the same call over REST at /api/v1/hapana with the same key and price, in JSON. Failed calls are free.
About $21 a monthfor a single-location boutique studio, 3,630 credits. Your Hapana plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning schedule read | 1 × 30 | 300 |
| Bookings and waitlist adds for callers | 1 × 60 | 600 |
| No-show fees after classes | 1 × 40 | 400 |
| Pending payments collected | 1 × 20 | 200 |
| Suspensions, cancellations, reactivations | 1 × 20 | 200 |
| Package credit top-ups and extensions | 1 × 15 | 150 |
| Instructor substitutions | 1 × 12 | 120 |
| Weekly member message | 2 × 4 | 80 |
| Payroll and delinquency reports | 2 × 4 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 213 calls | 3,630 |
The smallest pack, 5,000 credits for $29, covers this month. More locations and classes use more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Hapana API on Pro | Full read and write, all webhooks, metered premium actions. | Pro plan; you write, host and fix the client. |
| Hapana API on Premium | Read-only access and read webhooks. | No writes: no bookings, charges or membership changes. |
| Zapier and Middle | Hapana's listed connectors for workflow automation. | Triggers and steps you build; not an agent working in CORE. |
| Hapana Assistant | Queries the audit log, on Pro. | Inside Hapana only, not for ChatGPT or Claude. |
| By hand | Every screen in CORE and GROW. | One member at a time, at the desk. |
If you are on Pro and the Hapana API covers your job, use it: it is the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script working in CORE today, on any plan, from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Hapana tools.
Sign up free at https://cotlet.dev/signup?app=hapana, turn on Hapana under Integrations in the console and sign in at https://core.hapana.com/login in your Cloud Browser. Then connect your AI agent and ask it for today's schedule. The trial needs no card.
Hapana sells API access with its higher plans: Premium includes read-only API access with self-service keys and read webhooks, and Pro adds full read and write APIs, all webhooks and metered premium actions (pricing page, checked 15 Nov 2026). There is no Hapana MCP server and no official ChatGPT or Claude connector. Hapana also lists Zapier and Middle connectors. Cotlet does not use the API: it works in your own signed-in CORE account.
Yes, for what the tools cover: email campaigns, bulk SMS and contact import and export run in GROW, the rest in CORE. Sign in to both in the same Cloud Browser if your account uses both.
No. Hapana lists Hapana Assistant on its Pro plan for querying the audit log. Cotlet is separate: it lets ChatGPT, Claude or a script do studio work in your account over MCP or REST.
One with the role for the work: billing access for refunds and membership changes, schedule access for classes, Admin or Manager for the time clock. The agent can do only what that login can do.
Only in how it is called. Both carry the same 31 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Hapana.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy