Integrations & API

The Strava integration is included on Pro plans and above, and connections are rolling out now — if the Connect button is not yet available on your account, it will appear as we complete provider approval. Once connected, activities you record on Strava — runs, rides, swims, and more — are automatically imported into your Kounisou activity history.

To connect Strava:

1. Go to Settings → Integrations.
2. Click Connect Strava.
3. You will be redirected to Strava's authorisation page. Log in and approve the requested permissions.
4. You are returned to Kounisou with Strava shown as Connected.

After connection, new Strava activities sync automatically within a few minutes of being recorded. Historical activities from the past 30 days are imported on first connection. Each imported activity is labelled via Strava in your history. Coaches can see imported activities in Client Detail → Workouts for any client who has connected Strava.

To disconnect, return to Settings → Integrations and click Disconnect next to Strava. Previously imported activities remain in your history.

The Garmin integration is coming to Pro plans and above — connections are rolling out as we complete Garmin's developer-program approval. Once live, it imports activities recorded on Garmin devices and syncs health metrics such as heart rate variability and sleep data where available.

To connect Garmin:

1. Go to Settings → Integrations.
2. Click Connect Garmin.
3. You are redirected to Garmin Connect. Log in with your Garmin account and approve the permissions.
4. Return to Kounisou — Garmin will show as Connected.

Activities sync automatically after each Garmin device sync. If data does not appear after several hours, try disconnecting and reconnecting the integration, or check that your Garmin device has synced with the Garmin Connect app.

The Kounisou API is available on Pro plans (read-only, up to 1,000 requests/hour) and Studio and above (full read/write, up to 10,000 requests/hour). Enterprise plans have no rate limit.

To generate an API key:

1. Go to Settings → API.
2. Click Generate Key. Copy the key — it will not be shown again.
3. Include the key in the Authorization: Bearer <key> header with every request.

The full developer documentation lives at kounisou.com/developers and covers endpoints for clients, programs, check-ins, nutrition, calendar, messages, analytics, and webhooks, with a machine-readable OpenAPI spec at /api/v1/openapi.json. API keys can be revoked at any time from the API settings page.

Kounisou supports the Model Context Protocol (MCP) — the open standard that lets AI assistants like Claude work with your tools. Once connected, your assistant can list your clients, check adherence and nutrition, read check-in answers, and — on the Studio plan — send messages, assign programs, review check-ins, and add reminders. It only ever sees your own coaching data, and it acts with your API key's permissions, which you can revoke at any time.

To connect:

1. Go to Settings → API and generate an API key (Pro plan or above). Copy it — it is only shown once.
2. In your AI assistant, add Kounisou as an MCP server with the URL https://kounisou.com/api/mcp and the header Authorization: Bearer <your key>.
3. Ask it something like “Which of my clients need attention this week?” — it will use the Kounisou tools to answer.

Pro keys give your assistant read-only access; write actions (messaging clients, assigning programs) require a Studio key with write scope. Exact setup snippets for Claude and other clients are on the developers page. Treat API keys like passwords: use a separate key per assistant so you can revoke one without affecting the others.

Webhooks let your external systems receive real-time notifications when events happen in Kounisou — for example, when a client completes a workout, submits a check-in, or a payment succeeds. Webhooks are available on Pro plans (up to 5 endpoints) and Studio and above (unlimited).

To add a webhook endpoint:

1. Go to Settings → Webhooks → Add Endpoint.
2. Enter the URL that should receive POST requests.
3. Select the event types you want to subscribe to.
4. Save the endpoint. A signing secret is generated — use it to verify that incoming requests originate from Kounisou.

Each webhook delivery includes a payload with event type, timestamp, and relevant data. Failed deliveries are retried automatically up to three times with exponential back-off.

A Zapier integration is on our roadmap for Studio plans. Until it ships, you can build the same automations today with Webhooks and a tool like Make (formerly Integromat), or directly against the Kounisou API.