Health & fitness
My PT Hub
Clients, sessions, workouts, nutrition plans and packages in My PT Hub personal training software.
9 endpoints
PTminder publishes no public API and no MCP server (checked 14 Nov 2026). Cotlet runs a hosted PTminder MCP server with 32 tools that ChatGPT and Claude use in your own trainer account. Charges, texts and anything that reaches a client wait for your OK.
32 tools Read and write
PTminder publishes no public API: its website and Help Centre document no developer API. No PTminder MCP server and no official ChatGPT or Claude connector was verified.
| What you need | PTminder alone | Cotlet |
|---|---|---|
| Ask ChatGPT or Claude to do the work | No API or MCP server | Hosted MCP server |
| Reconcile, book and assign packages | By hand, client by client | 32 tools, writes after your OK |
| Balances, invoices and reports on a schedule | When you open the screen | On request or on a schedule |
| Run from n8n or a script | No public API | REST, same key |
Checked 14 Nov 2026. Sources: PTminder website · PTminder Help Centre · Help: Activate Stripe · Help: Accept payments with PayPal · Help: Sync the PTminder Calendar · Help: How to add a new client · Help: How to remove a client · Help: Client sessions and classes · Help: Sessions booked, completed and left · Help: Recording client notes · Help: Recording client assessments · Help: Booking in Sessions and Classes · Help: Available and Unavailable Time Windows · Help: Roster/Shift Working Hours · Help: Reconcile a past session/class · Help: The Workout Planner · Help: Recording/tracking workouts · Help: The Nutrition Planner · Help: Assigning a Package · Help: Assigning a Membership · Help: Modify package and membership credits · Help: Change or skip membership payments · Help: Stripe recurring card payments · Help: Once-off Stripe payment · Help: Once-off Ezidebit payment · Help: Record a payment transaction · Help: Send payment receipts · Help: Client invoices · Help: Check client balances · Help: Record and track expenses · Help: Discount Codes · Help: Direct Buy Links · Help: Sharing documents with clients · Help: Manual SMS messages · Help: Email Templates · Help: Sign Up Forms, Waivers, Questionnaires · Help: General Reports · Help: Financial Reports
Once, in a browser we host for you.
One address in its settings.
It reconciles yesterday, you approve the payments.
Your agent works in your own signed-in Cloud Browser. Card charges, texts and emails to clients wait for your OK. Who can see your session
Sign in to PTminder in a Cloud Browser. Open ptminder.com/login in your Cotlet Cloud Browser and sign in with your own trainer account, including the 6-digit code if PTminder asks for one.
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.
PTminder answers on the shared address https://cotlet.dev/mcp/v1, the same one as every other app you enable, so you add one connector for all of them. Turned PTminder on later? Refresh the connector and its 32 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: ptminder_read One tool per workflow in the PTminder Help Centre. Clients, balances and reports read at once; every tool that saves, sends or charges asks first.
Find, add or make inactive, read a client's summary and sessions, and keep private notes and assessments.
Most other tools take a client, so this is usually the first call. Read only, it runs without asking.
MCP callptminder_read → find_clients
REST endpointGET https://cotlet.dev/api/v1/ptminder/clients/find
| Name | Type | Description |
|---|---|---|
| query string | string | Part of a client name. Leave empty for all. |
| status string | string | Client Status, for example `active` or `inactive`. |
{
"clients": [
{
"client": "Example Client",
"status": "Active",
"phone": "+61 400 000 000"
},
{
"client": "Sample Member",
"status": "Active",
"phone": "+61 400 000 001"
}
]
} The same figures as the Summary button on the Clients tab. Use it before a renewal talk or when a client asks how many sessions are left.
MCP callptminder_read → get_client_summary
REST endpointGET https://cotlet.dev/api/v1/ptminder/client-summary
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
{
"client": "client"
} {
"client": "Example Client",
"package": "10 PT sessions",
"booked": 7,
"completed": 6,
"left": 3,
"paid": 800
} Reads Edit Client > Sessions & Classes.
MCP callptminder_read → list_client_sessions
REST endpointGET https://cotlet.dev/api/v1/ptminder/client-sessions
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| when string | string | `upcoming` or `past`. |
{
"client": "client"
} {
"client": "Example Client",
"sessions": [
{
"date": "2026-11-17T07:00",
"event": "PT session",
"status": "booked"
},
{
"date": "2026-11-20T07:00",
"event": "PT session",
"status": "booked"
}
]
} Run find_clients first so the same person is not added twice. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → add_client
REST endpointPOST https://cotlet.dev/api/v1/ptminder/clients
| Name | Type | Description |
|---|---|---|
| first_name string required | string | First name. |
| last_name string required | string | Last name. |
| fields object | object | Email, phone and the other optional client fields. |
{
"first_name": "first name",
"last_name": "last name"
} {
"client": "Example Client",
"status": "Active",
"saved": true
} PTminder recommends Inactive over deleting, so history stays and the client can be restored. The agent sets Inactive unless you ask to delete. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → remove_client
REST endpointDELETE https://cotlet.dev/api/v1/ptminder/clients
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| delete boolean | boolean | Permanently delete. Only works for an Inactive client and removes their history. |
{
"client": "client"
} {
"client": "Sample Runner",
"status": "Inactive",
"deleted": false
} Notes are visible to you only, never to the client. Newest notes show on top. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → record_client_note
REST endpointPOST https://cotlet.dev/api/v1/ptminder/client-notes
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| note string required | string | Note text. |
{
"client": "client",
"note": "note"
} {
"client": "Example Client",
"date": "2026-11-14",
"note": "Left knee sore, swap lunges for step-ups.",
"saved": true
} Assessments feed the client's progress graphs, which the client can also see in the Client Area and mobile apps. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → record_client_assessment
REST endpointPOST https://cotlet.dev/api/v1/ptminder/client-assessments
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| date string | string | ISO date. Defaults to today. |
| measurements object required | object | Standard fields (weight, height, age, blood pressure, girth, skin folds, body fat %) or your custom fields. |
| notes string | string | Assessment notes. |
{
"client": "client",
"measurements": "measurements"
} {
"client": "Example Client",
"date": "2026-11-14",
"weight_kg": 78.4,
"body_fat_percent": 21.5,
"saved": true
} Sessions and classes, availability windows, trainer rosters and the daily reconcile of past sessions.
Rostered hours apply: PTminder warns when a booking falls outside a trainer's working hours, and the agent passes that warning on. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → book_session
REST endpointPOST https://cotlet.dev/api/v1/ptminder/sessions
| Name | Type | Description |
|---|---|---|
| kind string required | string | `session` or `class`. |
| clients array | array | Clients for a session. Classes take sign-ups. |
| start string required | string | ISO date and time. |
| template string | string | A booking template from Services. |
| recurring object | object | Repeat rule for a recurring session. |
{
"kind": "kind",
"start": "start"
} {
"kind": "session",
"clients": [
"Example Client"
],
"start": "2026-11-17T07:00",
"recurring": "weekly",
"saved": true
} With online bookings allowed, clients can only request sessions inside available windows. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → set_availability
REST endpointPUT https://cotlet.dev/api/v1/ptminder/availability
| Name | Type | Description |
|---|---|---|
| type string required | string | `available` or `unavailable`. |
| start string required | string | ISO date and time. |
| end string required | string | ISO date and time. |
| description string | string | Shown to you only, never to clients. |
{
"type": "type",
"start": "start",
"end": "end"
} {
"type": "unavailable",
"start": "2026-11-24T12:00",
"end": "2026-11-24T14:00",
"description": "Admin block",
"saved": true
} Unrostered time is blocked on the trainer's Calendar, and clients cannot request online bookings outside it. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → set_trainer_roster
REST endpointPUT https://cotlet.dev/api/v1/ptminder/trainer-roster
| Name | Type | Description |
|---|---|---|
| trainer string required | string | Trainer as named in Trainers settings. |
| shifts array required | array | Day, start and end per shift. |
{
"trainer": "trainer",
"shifts": "shifts"
} {
"trainer": "Trainer A",
"shifts": [
{
"day": "Monday",
"start": "06:00",
"end": "11:00"
},
{
"day": "Monday",
"start": "16:00",
"end": "19:00"
}
],
"saved": true
} Reconciling feeds Reconciled Earnings. A payment through the stored card or account charges the client at once, so the agent shows the amount first. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → reconcile_session
REST endpointPOST https://cotlet.dev/api/v1/ptminder/session/reconcile
| Name | Type | Description |
|---|---|---|
| action string required | string | `list` or `reconcile`. `list` only reads. |
| session string | string | For `reconcile`: the past session or class, by date and time. |
| attendance object | object | Per client: `attended`, `missed`, `cancelled` or `rescheduled`, and whether to still charge a missed, cancelled or rescheduled one. |
| amount number | number | Amount charged to the client. |
| payment object | object | Optional: record a payment, or charge the stored card or account (Make a Payment, Pay by), and whether to email a receipt. |
{
"action": "reconcile",
"session": "2026-11-13T07:00 PT session",
"attendance": {
"Example Client": "attended"
},
"amount": 80,
"payment": {
"method": "cash",
"amount": 80,
"email_receipt": true
}
} {
"session": "2026-11-13T07:00 PT session",
"attendance": {
"Example Client": "attended"
},
"amount": 80,
"payment": {
"method": "cash",
"amount": 80,
"receipt_emailed": true
},
"reconciled": true
} Workouts from the exercise library, recorded results and nutrition plans for your clients.
The library has over 1,000 exercises with the muscles worked, steps and video links. Clients see assigned workouts in the Client Area and mobile apps. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → create_workout_plan
REST endpointPOST https://cotlet.dev/api/v1/ptminder/workout-plans
| Name | Type | Description |
|---|---|---|
| name string required | string | Workout name. |
| exercises array required | array | From the exercise library or your custom exercises, with sets, weights, reps and rest. |
| assign_to_clients array | array | Clients to assign it to. |
| assign_to_event string | string | A Calendar session or class to attach it to. |
{
"name": "Jane Doe",
"exercises": "exercises"
} {
"workout": "Lower body A",
"exercises": 5,
"assigned_to": [
"Example Client"
],
"saved": true
} Recorded workouts build the client's history and progress graphs. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → record_workout
REST endpointPOST https://cotlet.dev/api/v1/ptminder/workouts
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| workout string required | string | The assigned workout, or `unscheduled`. |
| results array required | array | Per exercise: the sets, reps and weights done. |
| use_previous boolean | boolean | Start from the last recorded values. |
{
"client": "client",
"workout": "workout",
"results": "results"
} {
"client": "Example Client",
"workout": "Lower body A",
"date": "2026-11-14",
"exercises": 5,
"completed": true
} The food library carries macro-nutrient values. Clients also see the plan in the Client Area and mobile apps. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → create_nutrition_plan
REST endpointPOST https://cotlet.dev/api/v1/ptminder/nutrition-plans
| Name | Type | Description |
|---|---|---|
| name string required | string | Plan name. |
| meals array required | array | Meals with food items from the library or your custom foods. |
| client string | string | Client to assign it to. |
| email_pdf boolean | boolean | Email the plan to the client as a PDF. |
{
"name": "Jane Doe",
"meals": "meals"
} {
"plan": "Cutting week one",
"meals": 5,
"client": "Example Client",
"emailed": false,
"saved": true
} Assign packages and memberships, change credits, skip periods and edit Stripe recurring payments.
A $0 package works as a make-up package for missed bookings, as the Help Centre suggests. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → assign_package
REST endpointPOST https://cotlet.dev/api/v1/ptminder/package/assign
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| package string required | string | Package from Services. |
| discount_code string | string | An existing discount code. |
| split_payments object | object | Optional split recurring payments, for example 4 weekly payments. Needs a payment integration and stored payment details. |
{
"client": "client",
"package": "package"
} {
"client": "Example Client",
"package": "10 PT sessions",
"price": 800,
"split_payments": null,
"saved": true
} The membership then shows its schedule, and can be paused or cancelled, on the client profile. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → assign_membership
REST endpointPOST https://cotlet.dev/api/v1/ptminder/membership/assign
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| membership string required | string | Membership from Services. |
| particulars object | object | Start date and the other membership settings you want changed. |
{
"client": "client",
"membership": "membership"
} {
"client": "Sample Member",
"membership": "Unlimited classes",
"start": "2026-11-17",
"saved": true
} Changes what the client can still book, so the agent shows old and new totals first. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → adjust_service_credits
REST endpointPOST https://cotlet.dev/api/v1/ptminder/service-credits/adjust
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| service string required | string | Assigned package or membership. |
| credits integer required | integer | New total of sessions or classes. |
{
"client": "client",
"service": "service",
"credits": 1
} {
"client": "Example Client",
"service": "10 PT sessions",
"credits_before": 10,
"credits_after": 11,
"saved": true
} This changes what the client pays, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → change_membership_payments
REST endpointPATCH https://cotlet.dev/api/v1/ptminder/membership-payments
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| membership string required | string | The client's membership. |
| change object required | object | A new fee for a period, `skip_credits` between two dates, or `skip_period`. |
{
"client": "client",
"membership": "membership",
"change": "change"
} {
"client": "Sample Member",
"membership": "Unlimited classes",
"skipped_period": "2026-12-22 to 2027-01-04",
"saved": true
} Works for stand-alone recurring payments and those linked to a membership. Money is involved, so each call waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → manage_recurring_card_payments
REST endpointPOST https://cotlet.dev/api/v1/ptminder/recurring-card-payments/manage
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| payment string required | string | The recurring payment series, or one period in it. |
| action string required | string | `edit_series`, `edit_period`, `skip_payment_and_charge` or `skip_payment_only`. |
| amount number | number | New amount, for the edit actions. |
{
"client": "client",
"payment": "payment",
"action": "action"
} {
"client": "Sample Member",
"payment": "Unlimited classes, weekly",
"action": "skip_payment_only",
"period": "2026-12-29",
"saved": true
} Clients apply the code in the Client Area store and mobile apps; you can apply it when assigning the item with assign_package. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → manage_discount_codes
REST endpointPOST https://cotlet.dev/api/v1/ptminder/discount-codes/manage
| Name | Type | Description |
|---|---|---|
| item string required | string | Package, membership or product in Services. |
| code string required | string | The promo code. |
| percent number required | number | Discount %. |
| uses_per_client integer | integer | How many times each client can use it for this item. |
{
"item": "item",
"code": "code",
"percent": 1
} {
"item": "10 PT sessions",
"code": "SPRING10",
"percent": 10,
"uses_per_client": 1,
"saved": true
} The link opens your Client Area store with that item, ready to buy. Use it in an email, a social post or your website.
MCP callptminder_read → get_store_buy_link
REST endpointGET https://cotlet.dev/api/v1/ptminder/store-buy-link
| Name | Type | Description |
|---|---|---|
| item string required | string | Package, membership or product name in Services. |
{
"item": "item"
} {
"item": "10 PT sessions",
"link": "https://example.com/store/10-pt-sessions"
} Balances, stored card charges, recorded payments with receipts, invoices, expenses and reports.
Reads the Finances tab. The breakdown shows each session or class charge and each payment behind the balance.
MCP callptminder_read → check_client_balances
REST endpointGET https://cotlet.dev/api/v1/ptminder/client-balances/check
| Name | Type | Description |
|---|---|---|
| client string | string | A client, for the breakdown of charges and payments. Leave empty for the full list. |
{
"balances": [
{
"client": "Example Client",
"amount_due": 240
},
{
"client": "Sample Member",
"amount_due": 95
},
{
"client": "Sample Runner",
"in_credit": 40
}
]
} Uses Finances > Payments with the stored card option ticked, and the card is charged immediately. It needs card or bank details the client or you already stored; the agent never enters card numbers. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → charge_stored_payment
REST endpointPOST https://cotlet.dev/api/v1/ptminder/stored-payment/charge
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| amount number required | number | Amount to charge. |
| notes string | string | Payment notes. |
| email_receipt boolean | boolean | Email the client a PDF receipt. |
{
"client": "client",
"amount": 1
} {
"client": "Example Client",
"amount": 240,
"method": "stored card",
"receipt_emailed": true,
"status": "paid"
} The payment shows under Payments Received and Transactions. Online purchases are recorded by PTminder already, so they need no call. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → record_payment
REST endpointPOST https://cotlet.dev/api/v1/ptminder/payments
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name, as find_clients returns it. |
| amount number required | number | Amount received. |
| method string required | string | How the client paid, for example cash or bank transfer. |
| date string | string | ISO date. Defaults to today. |
| email_receipt boolean | boolean | Email the client a PDF receipt. |
{
"client": "client",
"amount": 1,
"method": "method"
} {
"client": "Sample Member",
"amount": 95,
"method": "bank transfer",
"receipt_emailed": true,
"saved": true
} The Status badge shows Paid, Not Paid or Partially Paid. Creating and emailing are separate calls, so you can read the invoice before it goes out. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → manage_invoices
REST endpointPOST https://cotlet.dev/api/v1/ptminder/invoices/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `list`, `create`, `email` or `assign_payment`. `list` only reads. |
| client string | string | Client, for `create` and `list`. |
| invoice string | string | Invoice number, for `email` and `assign_payment`. |
| lines array | array | For `create`: description and amount per line. |
| payment string | string | For `assign_payment`: an existing recorded payment. |
{
"action": "action"
} {
"invoice": "INV-0412",
"client": "Example Client",
"lines": [
{
"description": "3 PT sessions",
"amount": 240
}
],
"status": "Not Paid",
"emailed": false
} Expenses count in the Profit report. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → record_expense
REST endpointPOST https://cotlet.dev/api/v1/ptminder/expenses
| Name | Type | Description |
|---|---|---|
| description string required | string | For example gym rental, travel or equipment. |
| amount number required | number | Amount. |
| date string | string | ISO date. |
| recurring string | string | Repeat rule for an ongoing expense. |
{
"description": "description",
"amount": 1
} {
"description": "Gym rental",
"amount": 600,
"recurring": "monthly",
"saved": true
} Reconciled Earnings counts only reconciled sessions, so reconcile first. Projected Earnings includes future bookings and scheduled membership renewals.
MCP callptminder_read → run_financial_report
REST endpointGET https://cotlet.dev/api/v1/ptminder/financial-reports/run
| Name | Type | Description |
|---|---|---|
| report string required | string | `payments_recorded`, `reconciled_earnings`, `projected_earnings`, `expenses` or `profit`. |
| from string | string | ISO date. |
| to string | string | ISO date. |
{
"report": "report"
} {
"report": "profit",
"from": "2026-10-01",
"to": "2026-10-31",
"income": 18650,
"expenses": 2400,
"profit": 16250
} Returns the report as rows. PTminder can also export it as PDF, Excel or CSV.
MCP callptminder_read → run_general_report
REST endpointGET https://cotlet.dev/api/v1/ptminder/general-reports/run
| Name | Type | Description |
|---|---|---|
| report string required | string | `summary`, `daily_schedule`, `session_class_summary` or `client_list`. |
| from string | string | ISO date. |
| to string | string | ISO date. |
| filters object | object | The report's own filters, for example client status or trainer. |
{
"report": "report"
} {
"report": "summary",
"from": "2026-10-01",
"to": "2026-10-31",
"active_clients": 42,
"bookings": 310,
"payments": 18650,
"expenses": 2400
} Manual SMS, shared documents, the 18 email templates and your sign-up forms and waivers.
Needs SMS credits from an SMS package in PTminder. The agent shows recipients and text before sending. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → send_sms
REST endpointPOST https://cotlet.dev/api/v1/ptminder/sms
| Name | Type | Description |
|---|---|---|
| recipients array required | array | Clients or client groups. |
| message string required | string | Message text. |
{
"recipients": "recipients",
"message": "message"
} {
"recipients": 2,
"message": "Reminder: your balance is due this week. Thanks!",
"sent": true
} Templates reach every client who gets that email, so a change waits for your OK. Reset to Default undoes it. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → edit_email_template
REST endpointPATCH https://cotlet.dev/api/v1/ptminder/email-template
| Name | Type | Description |
|---|---|---|
| template string required | string | For example booking confirmation, session reminder, payment receipt or invoice. |
| content string required | string | New text, with the placeholders PTminder lists. |
| reset boolean | boolean | Reset to Default instead. |
{
"template": "template",
"content": "content"
} {
"template": "Session reminder",
"saved": true
} Lives in Settings > Client Area > Client Form Setup; custom forms need the Form Builder turned on. New clients see the form when they sign up online. By default you confirm each call; you can switch that off for this tool.
MCP callptminder_write → edit_signup_form
REST endpointPATCH https://cotlet.dev/api/v1/ptminder/signup-form
| Name | Type | Description |
|---|---|---|
| form string required | string | `default` or the name of a custom form. |
| fields array required | array | Questions, checkboxes, information blocks or a digital signature, in order, and which are mandatory. |
{
"form": "form",
"fields": "fields"
} {
"form": "PAR-Q",
"fields": 8,
"saved": true
} Your signed-in PTminder browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 32 PTminder tools. The session cookie stays in the Cloud Browser.
The clients, bookings, assessments and finances your PTminder account can open, and nothing more.
Card and bank numbers, your Stripe, Ezidebit and PayPal connections, calendar sync and your PTminder plan.
You sign in again yourself, with your code if asked, in the same Cloud Browser.
Disable PTminder for agents, reset the browser, or change your PTminder password.
You type your PTminder password and any sign-in code yourself; the agent only uses the session that sign-in 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 PTminder server when PTminder changes its screens, so reconciling and bookings keep working without a change on your side.
New PTminder features become available to the agent. It still sees only what your own PTminder account can see.
Cotlet never sees or stores your password. If PTminder 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 |
|---|---|
| Package or membership credits | Call adjust_service_credits again with the earlier total |
| Client set Inactive | Set them back to active in PTminder; history stays |
| Email template | Reset to Default with edit_email_template |
| Stored card charge, SMS or emailed receipt | Already with your client: sort it out with them directly |
All 25 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 7 read tools, clients, balances, reports and store links, run at once.
{
"name": "reconcile_session",
"arguments": {
"action": "reconcile",
"session": "2026-11-13T07:00 PT session",
"attendance": {
"Example Client": "attended"
},
"amount": 80,
"payment": {
"method": "cash",
"amount": 80,
"email_receipt": true
}
}
} curl -X POST https://cotlet.dev/api/v1/ptminder/session/reconcile \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"reconcile","session":"2026-11-13T07:00 PT session","attendance":{"Example Client":"attended"},"amount":80,"payment":{"method":"cash","amount":80,"email_receipt":true}}' {
"session": "2026-11-13T07:00 PT session",
"attendance": {
"Example Client": "attended"
},
"amount": 80,
"payment": {
"method": "cash",
"amount": 80,
"receipt_emailed": true
},
"reconciled": true
} The example reconciles one 7am PT session: the client attended, paid $80 in cash and gets the receipt by email. A cron job or n8n flow can make the same call over REST at /api/v1/ptminder with the same key and price, in JSON. Failed calls are free.
About $22 a monthfor a personal trainer with about forty clients, 3,760 credits. Your PTminder plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning reconcile of yesterday's sessions | 6 × 20 | 1,200 |
| New clients with a package and bookings | 4 × 4 | 160 |
| Monday balance check, invoices and texts | 4 × 4 | 160 |
| Workout plans and recorded workouts | 1 × 40 | 400 |
| Client notes and assessments | 1 × 20 | 200 |
| Membership skips and credit changes | 2 × 6 | 120 |
| Month-end Profit and Summary reports | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 226 calls | 3,760 |
The smallest pack, 5,000 credits for $29, covers this month. A studio with several trainers uses 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 |
|---|---|---|
| PTminder automatic emails and SMS reminders | Booking confirmations, session reminders, receipts and waiting list notices. | Fixed messages from templates; no agent decides or acts. |
| Calendar sync | Copies your PTminder Calendar one way to iCal, Outlook or Google Calendar. | Read only in the other calendar; nothing comes back. |
| By hand | Open the Dashboard, Clients and Finances tabs and click through. | Only between sessions, at the screen. |
Keep PTminder's own reminders and calendar sync where they already do the job. Cotlet fits when you want ChatGPT, Claude or a script doing the reconciling, bookings and payment admin on request or on a schedule, 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 PTminder tools.
Sign up free at https://cotlet.dev/signup?app=ptminder, turn on PTminder under Integrations in the console and sign in at https://ptminder.com/login/ in your Cloud Browser. Then connect your AI agent and ask it who owes you money. The trial needs no card.
PTminder publishes no public API: its website and Help Centre document no developer API (checked 14 Nov 2026). No PTminder MCP server and no official ChatGPT or Claude connector was verified. Cotlet does not need one: it works in your own signed-in PTminder account.
No. Clients add their own card or bank details in the Client Area or mobile apps, or you add them in PTminder. charge_stored_payment charges details that are already stored; no tool enters card numbers.
PTminder's Reconciled Earnings report counts only reconciled sessions and classes, as its Help Centre explains. reconcile_session keeps that report complete.
The trainer account whose clients the agent should work with. The agent sees only what that account sees in PTminder, and the PTminder sign-in code, if asked, is typed by you.
Only in how it is called. Both carry the same 32 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 PTminder.
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