[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own Buildertrend API

> Buildertrend's API is in early access with a waitlist. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/buildertrend

Buildertrend's API is in early access with a waitlist (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Buildertrend 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 Buildertrend session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=buildertrend)

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

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

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/schedule-for-week" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"job": "Oak St"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/schedule-for-week";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ job: "Oak St" }),
});
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/schedule-for-week",
headers={"Authorization": f"Bearer {key}"},
json={"job": "Oak St"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"date": "2026-11-26",
"item": "Roof sheathing",
"assigned_to": "Ridge Framing",
"status": "scheduled"
},
{
"date": "2026-11-27",
"item": "Window install",
"assigned_to": "Clear View Windows",
"status": "scheduled"
}
]
}
```

01 Build

## How do you build a Buildertrend endpoint with Cotlet?

1. 01  
buildertrend.net  
Signed in  
### Sign in to Buildertrend in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List this week's schedule items for the Oak St job with date, item, assignee and status.  
### Do the job once with your agent.  
For example: "List this week's schedule items for the Oak St job with date, item, assignee and status."
3. 03  
Save endpoint  
Name  
schedule-for-week  
Input  
job  
Returns  
date, item, assigned\_to, status  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a job or a week, and the fields it returns.
4. 04  
$ POST /api/v1/custom/schedule-for-week  
200 OK  
### 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 Buildertrend session.

02 Endpoints

## Example endpoints you could build for Buildertrend

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

- POST `/api/v1/custom/schedule-for-week`  
### Schedule for a week  
Date, item, assignee and status of each schedule item
- POST `/api/v1/custom/past-due-items`  
### Past due items  
Schedule items past their date, by job
- POST `/api/v1/custom/pending-selections`  
### Selections waiting  
Selections the client has not made yet
- POST `/api/v1/custom/open-change-orders`  
### Open change orders  
Change orders waiting for approval, with amounts
- POST `/api/v1/custom/add-daily-log` writes  
### Add a daily log  
A daily log on the job you name, with your notes
- POST `/api/v1/custom/<name>`

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

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/schedule-for-week" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"job": "Oak St"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"date": "2026-11-26",
"item": "Roof sheathing",
"assigned_to": "Ridge Framing",
"status": "scheduled"
},
{
"date": "2026-11-27",
"item": "Window install",
"assigned_to": "Clear View Windows",
"status": "scheduled"
}
]
}
```

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

- Schedule Cotlet endpoint Slack or email  
### A Monday look-ahead.  
Each job's schedule for the week, sent to your crews in Slack or by email.
- Friday endpoint Email  
### A client update.  
Pending selections and change orders, sent to each client every Friday.
- Website or HubSpot endpoint lead opportunity  
### Web and HubSpot leads into Buildertrend.  
A lead from your website form or HubSpot becomes a Buildertrend lead opportunity with the contact and project notes.
- Voice or chat agent endpoint schedule  
### Your own AI assistant.  
A voice or chat agent that reads a job's schedule before it answers a client.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Buildertrend session, so it can read and change only what your Buildertrend 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.

DRY RUN · nothing sent

$ POST /api/v1/custom/add-daily-log

would POST buildertrend.net/... add a daily log to the Oak St job

`add-daily-log`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Buildertrend have an official API?

Buildertrend has an API on its developer portal, in early access with a waitlist (checked 20 Nov 2026). Its marketplace lists integrations such as HubSpot, Salesforce and Gusto. The full picture with sources: [Does Buildertrend have an API or MCP server?](https://cotlet.dev/api-status/buildertrend.md)

Want ChatGPT or Claude to work in Buildertrend instead of code? See the [Buildertrend MCP server](https://cotlet.dev/integrations/buildertrend-api-mcp-server.md).

1/3

Official API

Early access

[Full API & MCP report](https://cotlet.dev/api-status/buildertrend.md)

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.

## Buildertrend API with Cotlet: questions

### Is this an official Buildertrend API?

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

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

POST /api/v1/custom/<name>

## Build your first Buildertrend endpoint

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

[Try it free now](https://cotlet.dev/app/signup?app=buildertrend)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
