QuickCoach API · unofficial, by Cotlet

Create your own QuickCoach API

QuickCoach: no API or developer docs found on quickcoach.fit or in its help index (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your QuickCoach 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 QuickCoach 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 QuickCoach. QuickCoach is a trademark of its owner. If QuickCoach's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/clients-without-plan" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week": "2026-11-23"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/clients-without-plan";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ week: "2026-11-23" }),
});
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/clients-without-plan",
    headers={"Authorization": f"Bearer {key}"},
    json={"week": "2026-11-23"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "client": "Jess M.",
      "last_week": "Week 6",
      "sessions_done": 4,
      "sessions_planned": 4
    },
    {
      "client": "Ana R.",
      "last_week": "Week 8",
      "sessions_done": 2,
      "sessions_planned": 4
    }
  ]
}

01 Build

How do you build a QuickCoach endpoint with Cotlet?

  1. Sign in to QuickCoach 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 with no plan published for the week, with their last completed week."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a week 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 QuickCoach session.

02 Endpoints

Example endpoints you could build for QuickCoach

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

  • POST /api/v1/custom/clients-without-plan

    Clients without a plan

    Clients with nothing published for a week

  • POST /api/v1/custom/skipped-sessions

    Skipped sessions

    Clients and the sessions they skipped in a week

  • POST /api/v1/custom/todays-check-ins

    Today's check-ins

    Check-ins waiting for a reply, with the client

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

    Client habits

    Habits assigned to a client

  • POST /api/v1/custom/add-habit writes

    Add a habit to a client

    A habit from your library added to a client

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/clients-without-plan" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week": "2026-11-23"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "client": "Jess M.",
      "last_week": "Week 6",
      "sessions_done": 4,
      "sessions_planned": 4
    },
    {
      "client": "Ana R.",
      "last_week": "Week 8",
      "sessions_done": 2,
      "sessions_planned": 4
    }
  ]
}

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 QuickCoach endpoints for?

  • Schedule Cotlet endpoint Email

    A Sunday planning list.

    Clients with no plan for the week, sent to you by email.

  • Schedule endpoint Slack

    Check-ins in Slack.

    Today's check-ins posted for you and your assistant coach.

  • Schedule endpoint Google Sheets

    A client sheet.

    Clients, plans and skipped sessions pulled into Google Sheets weekly.

  • Chat agent endpoint client week

    Your own check-in assistant.

    A chat agent that reads a client's week before it drafts a reply.

04 Access

What can an endpoint see and change?

An endpoint works in your own QuickCoach session, so it can read and change only what your QuickCoach 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 habit to a client, 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 QuickCoach have an official API?

QuickCoach: no API, webhooks or data export found on quickcoach.fit, in its help index for agents or in its llms.txt (checked 20 Nov 2026). The full picture with sources: Does QuickCoach have an API or MCP server?

Want ChatGPT or Claude to work in QuickCoach instead of code? See the QuickCoach 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.

QuickCoach API with Cotlet: questions

Is this an official QuickCoach API?

No. Cotlet is independent and not affiliated with QuickCoach. The endpoints you build run in your own signed-in QuickCoach 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 QuickCoach changes its screens?

An endpoint works while QuickCoach works the way it did when you built it. If QuickCoach 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 QuickCoach 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.