17hats API · unofficial, by Cotlet

Create your own 17hats API

17hats: no public API found in the 17hats help center (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your 17hats 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 17hats 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 17hats. 17hats is a trademark of its owner. If 17hats's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/overdue-invoices" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days_overdue": 30}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/overdue-invoices";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ days_overdue: 30 }),
});
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/overdue-invoices",
    headers={"Authorization": f"Bearer {key}"},
    json={"days_overdue": 30},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "invoice": "214",
      "client": "Dana R.",
      "project": "Family session",
      "amount": 650,
      "days_overdue": 58
    },
    {
      "invoice": "221",
      "client": "Tom H.",
      "project": "Headshots",
      "amount": 320,
      "days_overdue": 45
    }
  ]
}

01 Build

How do you build a 17hats endpoint with Cotlet?

  1. Sign in to 17hats 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 invoices more than 30 days overdue with the client, project and amount."

  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 17hats session.

02 Endpoints

Example endpoints you could build for 17hats

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

  • POST /api/v1/custom/overdue-invoices

    Overdue invoices

    Client, project, amount and days overdue of each open invoice

  • POST /api/v1/custom/new-leads

    New leads

    Leads from a period with their source and notes

  • POST /api/v1/custom/unsigned-contracts

    Unsigned contracts

    Contracts sent and not yet signed, with the date sent

  • POST /api/v1/custom/projects-by-date

    Projects by date

    Projects with a session or due date in a period

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

    Add a lead

    A new lead with name, email and a note

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/overdue-invoices" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days_overdue": 30}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "invoice": "214",
      "client": "Dana R.",
      "project": "Family session",
      "amount": 650,
      "days_overdue": 58
    },
    {
      "invoice": "221",
      "client": "Tom H.",
      "project": "Headshots",
      "amount": 320,
      "days_overdue": 45
    }
  ]
}

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 17hats endpoints for?

  • Monday Cotlet endpoint Email

    A weekly money report.

    Overdue invoices and payments received, sent to your email every Monday.

  • Website form endpoint 17hats lead

    Leads from your own forms.

    Each inquiry from your website or ads, saved in 17hats as a lead.

  • Schedule endpoint Google Sheets

    A bookings sheet.

    Projects and their dates pulled into Google Sheets on a schedule.

  • Chat agent endpoint invoices

    Your own AI assistant.

    A chat agent that checks a client's invoices and contract before it answers.

04 Access

What can an endpoint see and change?

An endpoint works in your own 17hats session, so it can read and change only what your 17hats 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 lead, 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 17hats have an official API?

17hats: no public API, developer docs or webhooks found in the 17hats help center (checked 20 Nov 2026). Its Zapier app and CSV export cover contacts only. The full picture with sources: Does 17hats have an API or MCP server?

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

17hats API with Cotlet: questions

Is this an official 17hats API?

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

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