API and webhooks

API and Webhooks Overview

The HubFit API lets your own software read and update your coaching data: your website's sign-up form can add clients, a dashboard can show this week's check-ins, a script can message clients or add tasks. Webhooks work the other way round, sending an event to your server the moment something happens in HubFit.

The API and webhooks are on the Ultimate plan. To connect AI assistants such as Claude and ChatGPT instead, see HubFit MCP, which is on every paid plan.

Everything a developer needs, from the first request to every endpoint, is in the API docs.

Creating an API Key

Only the workspace owner can create API keys.

Go to Settings > API

Click Create key and give it a name that says what will use it, such as "Website sign-up form"

Under Permissions, choose only what it needs. Read clients is on by default

Under Expires, choose 30 days, 90 days, 1 year or no expiry

Click Copy and store the key somewhere safe, such as your password manager or your tool's secret settings

HubFit shows a key only once, when it's created. Anyone with the key can do whatever its permissions allow, so never paste it into a website's code, an email or a chat.

Permission	Lets the key
Read clients	See your clients, what they log, check-ins, health data, notes and purchases
Update clients	Add notes to your clients
Add clients	Add new clients and send them their login details
Review check-ins	Mark check-ins reviewed, with an optional comment
Message clients	Send chat messages to your clients as you
Manage tasks	See, add and update your team's tasks
Manage on-demand access	Give clients access to on-demand content, or remove it
Manage webhooks	Send client events to a URL as they happen

To replace a key, create a new one, switch your tool over to it, then revoke the old one in Settings > API. A revoked or expired key stops working straight away.

Adding a Webhook

Go to Settings > API and click Add webhook

Paste the URL that should receive the events

Under Events, choose what to send

Event	Sent when
Client added	A client is added to your workspace
Check-in submitted	A client submits a check-in
Questionnaire submitted	A client fills in a questionnaire
Workout completed	A client finishes a workout
Package purchased	A client completes checkout for one of your packages

Each event carries ids, not your clients' details: your server fetches the record with an API key. Every event is signed with the endpoint's signing secret, so your server can check it came from HubFit. The webhooks guide shows how.

Deliveries and Retries

Open a webhook in Settings > API to see what was sent to it in the last 30 days, with each response.

If your server doesn't reply with a success within 10 seconds, HubFit tries again after 1 minute, 1 hour and 6 hours
A webhook that gets no success for 5 days is turned off. Turn it back on in Settings once your server is fixed; events from while it was off aren't sent
A workspace can have up to 10 webhooks

Limits

Limit	Amount
Requests	120 a minute per coach, shared with HubFit MCP

If your workspace needs more, contact support.

Zapier, MCP or the API?

You want to	Use
Connect HubFit to other apps without code	Zapier
Ask about your clients in Claude, ChatGPT or another assistant	HubFit MCP
Build your own integration, dashboard or script	The API and webhooks