FitSW API · unofficial, by Cotlet

Create your own FitSW API

FitSW: no public API or developer docs found on fitsw.com (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your FitSW account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in FitSW session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by FitSW. FitSW is a trademark of its owner. If FitSW's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/programs-ending" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days": 7}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/programs-ending";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ days: 7 }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/programs-ending",
    headers={"Authorization": f"Bearer {key}"},
    json={"days": 7},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "client": "Jess M.",
      "program": "Base 6 weeks",
      "ends": "2026-11-23",
      "workouts_done": "17 of 18"
    },
    {
      "client": "Omar S.",
      "program": "Base 6 weeks",
      "ends": "2026-11-23",
      "workouts_done": "18 of 18"
    }
  ]
}

01 Build

How do you build a FitSW endpoint with Cotlet?

  1. Sign in to FitSW in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List the clients whose program ends in the next 7 days, with the program and the workouts completed."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a number of days or a client, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in FitSW session.

02 Endpoints

Example endpoints you could build for FitSW

Cotlet ships no fixed list of FitSW endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/programs-ending

    Programs ending soon

    Clients whose program ends in the days you name, with workouts done

  • POST /api/v1/custom/quiet-clients

    Clients who went quiet

    Clients with no workout in the days you name

  • POST /api/v1/custom/client-progress

    Client progress

    A client's tracked metrics for a period

  • POST /api/v1/custom/payments

    Payments

    Client payments in the days you name

  • POST /api/v1/custom/client-note writes

    Add a client note

    A note added to the client you name

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/programs-ending" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days": 7}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "client": "Jess M.",
      "program": "Base 6 weeks",
      "ends": "2026-11-23",
      "workouts_done": "17 of 18"
    },
    {
      "client": "Omar S.",
      "program": "Base 6 weeks",
      "ends": "2026-11-23",
      "workouts_done": "18 of 18"
    }
  ]
}

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

What can you use your FitSW endpoints for?

  • Schedule Cotlet endpoint Slack or email

    A Monday client list in n8n or Make.

    Programs ending and clients who went quiet, sent to Slack or email.

  • Month end endpoint Progress report

    Monthly progress reports.

    Each client's tracked metrics for the month, pulled into the report you send yourself.

  • Schedule endpoint Google Sheets

    A payments sheet.

    Client payments by month, pulled into Google Sheets.

  • Chat agent endpoint workouts

    Your own AI assistant.

    A chat agent that checks a client's last workouts before it answers them.

04 Access

What can an endpoint see and change?

An endpoint works in your own FitSW session, so it can read and change only what your FitSW login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as adding a client note, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

05 Official API

Does FitSW have an official API?

FitSW: no public API, developer docs, Zapier app or webhooks found (checked 20 Nov 2026). The full picture with sources: Does FitSW have an API or MCP server?

Want ChatGPT or Claude to work in FitSW instead of code? See the FitSW MCP server.

06 Pricing

What does it cost?

per successful call
10 credits
when a call fails
0
in the smallest pack
≈ 500 calls
free trial, no card
7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

FitSW API with Cotlet: questions

Is this an official FitSW API?

No. Cotlet is independent and not affiliated with FitSW. The endpoints you build run in your own signed-in FitSW account.

Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

What happens when FitSW changes its screens?

An endpoint works while FitSW works the way it did when you built it. If FitSW changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

Build your first FitSW endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.