BuildBook API · unofficial, by Cotlet

Create your own BuildBook API

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

curl
curl -X POST "https://cotlet.dev/api/v1/custom/tasks-for-week" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week_of": "2026-11-23"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/tasks-for-week";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ week_of: "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/tasks-for-week",
    headers={"Authorization": f"Bearer {key}"},
    json={"week_of": "2026-11-23"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "day": "Thu",
      "project": "Patel addition",
      "task": "Pour patio slab",
      "start": "07:00"
    },
    {
      "day": "Thu",
      "project": "Ruiz deck",
      "task": "Frame deck",
      "start": "08:00"
    }
  ]
}

01 Build

How do you build a BuildBook endpoint with Cotlet?

  1. Sign in to BuildBook 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 scheduled tasks for this week with the day, project and task."

  3. Save it as an endpoint.

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

02 Endpoints

Example endpoints you could build for BuildBook

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

  • POST /api/v1/custom/tasks-for-week

    Tasks for a week

    Day, project, task and start time of each scheduled task

  • POST /api/v1/custom/budget-status

    Budget status

    A project's budget against actuals, by cost code

  • POST /api/v1/custom/leads-by-stage

    Leads by stage

    Each lead with its stage and last activity

  • POST /api/v1/custom/daily-logs

    Daily logs

    The logs of a project for the dates you name

  • POST /api/v1/custom/add-daily-log writes

    Add a daily log

    A daily log saved on the project you name

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

Request

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

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "day": "Thu",
      "project": "Patel addition",
      "task": "Pour patio slab",
      "start": "07:00"
    },
    {
      "day": "Thu",
      "project": "Ruiz deck",
      "task": "Frame deck",
      "start": "08:00"
    }
  ]
}

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

  • Schedule Cotlet endpoint Slack or email

    A Friday crew plan in n8n or Make.

    Next week's tasks by project, sent to Slack or email.

  • Chat message endpoint daily log

    Logs from the field.

    A message from your site lead becomes a daily log on the right project.

  • Schedule endpoint Google Sheets

    A dashboard or a sheet.

    Budget against actuals for every project, pulled into Google Sheets.

  • Voice or chat agent endpoint next task

    Your own AI receptionist.

    A phone or chat agent that checks a project's next task before it answers a client.

04 Access

What can an endpoint see and change?

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

BuildBook: no API or webhooks found on buildbook.co or in its help center (checked 20 Nov 2026). It connects to QuickBooks and exports a budget to Excel. The full picture with sources: Does BuildBook have an API or MCP server?

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

BuildBook API with Cotlet: questions

Is this an official BuildBook API?

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

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