[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 Housecall Pro API

> Housecall Pro's API key is for the MAX plan only, with limited access. 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/housecall-pro

Housecall Pro's API key is for MAX plan accounts only, with limited access (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Housecall Pro 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 Housecall Pro session and returns only what your login can see.

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

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

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

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/jobs-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
```

Node.js

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

Response 200 OK · JSON

```
{
"data": [
{
"time": "08:00",
"technician": "Leo",
"customer": "Dana W.",
"address": "14 Birch Rd",
"job": "Water heater install"
},
{
"time": "10:30",
"technician": "Leo",
"customer": "Tom H.",
"address": "7 Lake St",
"job": "AC tune-up"
}
]
}
```

01 Build

## How do you build a Housecall Pro endpoint with Cotlet?

1. 01  
pro.housecallpro.com  
Signed in  
### Sign in to Housecall Pro in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List tomorrow's jobs with the technician, customer, address and time.  
### Do the job once with your agent.  
For example: "List tomorrow's jobs with the technician, customer, address and time."
3. 03  
Save endpoint  
Name  
jobs-for-day  
Input  
date  
Returns  
time, technician, customer, address, job  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a date or a technician, and the fields it returns.
4. 04  
$ POST /api/v1/custom/jobs-for-day  
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 Housecall Pro session.

02 Endpoints

## Example endpoints you could build for Housecall Pro

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

- POST `/api/v1/custom/jobs-for-day`  
### Jobs for a day  
Time, technician, customer, address and job for each scheduled job
- POST `/api/v1/custom/unscheduled-jobs`  
### Unscheduled jobs  
Jobs still waiting for a date, oldest first
- POST `/api/v1/custom/past-due-invoices`  
### Past-due invoices  
Customer, amount due and last sent date of each open invoice past its due date
- POST `/api/v1/custom/find-customer`  
### Find a customer  
Matching customers with phone, email, address and last job
- POST `/api/v1/custom/add-job-note` writes  
### Add a job note  
A note on the job you name, seen by your team
- 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/jobs-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
```

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

Response · 200 OK

```
{
"data": [
{
"time": "08:00",
"technician": "Leo",
"customer": "Dana W.",
"address": "14 Birch Rd",
"job": "Water heater install"
},
{
"time": "10:30",
"technician": "Leo",
"customer": "Tom H.",
"address": "7 Lake St",
"job": "AC tune-up"
}
]
}
```

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 Housecall Pro endpoints for?

- Schedule Cotlet endpoint Slack or email  
### An evening dispatch sheet in n8n or Make.  
Tomorrow's jobs per technician, sent to Slack or email each evening.
- Website form endpoint customers  
### A request form on your own website.  
A new request checked against your customers in Housecall Pro before you call back.
- Schedule endpoint Google Sheets  
### A collections sheet.  
Past-due invoices pulled into Google Sheets each Monday.
- Voice or chat agent endpoint jobs  
### Your own AI receptionist.  
A voice or chat agent that finds the caller's customer record and next job before it answers.

04 Access

## What can an endpoint see and change?

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

DRY RUN · nothing sent

$ POST /api/v1/custom/add-job-note

would POST pro.housecallpro.com/... add a note to the 08:00 job for Dana W.

`add-job-note`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Housecall Pro have an official API?

Housecall Pro gives an API key with limited access to MAX plan accounts only; its docs list creating and reading customers, employees and jobs, and MAX accounts can turn on webhooks (checked 20 Nov 2026). Its Zapier app has two triggers and one action. The full picture with sources: [Does Housecall Pro have an API or MCP server?](https://cotlet.dev/api-status/housecall-pro.md)

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

2/3

Official API

MAX plan

[Full API & MCP report](https://cotlet.dev/api-status/housecall-pro.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.

## Housecall Pro API with Cotlet: questions

### Is this an official Housecall Pro API?

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

An endpoint works while Housecall Pro works the way it did when you built it. If Housecall Pro 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 Housecall Pro 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=housecall-pro)

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.
