[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.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)

# Housecall Pro API and MCP server

> Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026). The public reference documents reads for invoices and a job create call; it documents no call to create, send or pay an invoice, and Housecall Pro publishes no MCP server.

Field service software for home-service businesses such as plumbers, electricians and HVAC: customers, estimates with options, scheduled and dispatched jobs, invoices and payments.

## What is the Housecall Pro API?

Cotlet's Housecall Pro API exposes 15 endpoints for your own Housecall Pro account: list customers, list jobs, get job, list estimates, list invoices, get invoice, list price book, create customer, create job, create estimate, add estimate option, send estimate, create progress invoice, send invoice and record invoice payment. The list_customers endpoint returns search customers by name, email, phone or address, with their service addresses. Each endpoint takes simple JSON inputs like limit, cursor or customer_id and works both as an operation of the housecall_pro_read or housecall_pro_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 15 (7 read, 8 write)
- **Updated:** 2026-10-18

Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026). Cotlet is a hosted MCP server and REST API for Housecall Pro with 15 endpoints (7 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Housecall Pro have an official API?

Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026). The public reference documents reads for invoices and a job create call; it documents no call to create, send or pay an invoice, and Housecall Pro publishes no MCP server.

| Task | Housecall Pro official | Cotlet |
|---|---|---|
| Read invoices and their status | Yes: Get Invoices and Get Job Invoices, MAX plan only | Yes |
| Create a job | Yes: Create a Job takes line items, MAX plan only | Yes |
| Read an estimate | Yes: Get a single estimate by ID, MAX plan only | Yes |
| Create a customer | Partly: The Zapier app has a Create New Customer action | Yes |
| Create an estimate with options | Partly: MAX plan only, with a limited-access key | Yes |
| Create a progress invoice for part of a job | No | Yes |
| Send an invoice to the customer | No: An invoice.sent webhook event exists, no send call | Yes |
| Record a payment on an invoice | No | Yes |

Sources: [Housecall Pro Public API reference](https://docs.housecallpro.com/docs/housecall-public-api), [Housecall Pro Help: FAQs about HCP Data (API key on MAX)](https://help.housecallpro.com/en/articles/5449431-faqs-about-hcp-data), [Housecall Pro Help: Zapier Integration Overview](https://help.housecallpro.com/en/articles/5452973-zapier-integration-overview), [Housecall Pro Help: Send an Invoice](https://help.housecallpro.com/en/articles/2876243-send-an-invoice)

## For AI agents

```text
Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026). The public reference documents reads for invoices and a job create call; it documents no call to create, send or pay an invoice, and Housecall Pro publishes no MCP server.
Cotlet provides a hosted MCP server and REST API for Housecall Pro: 15 tools (7 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=housecall-pro, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    housecall_pro_read, housecall_pro_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/housecall-pro, each operation at its own route, e.g. POST /api/v1/housecall-pro/invoices/{invoice_id}
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_customers, list_jobs, get_job, list_estimates, list_invoices, get_invoice, list_price_book, create_customer, create_job, create_estimate, add_estimate_option, send_estimate, create_progress_invoice, send_invoice, record_invoice_payment
Confirm      create_customer, create_job, create_estimate, send_estimate, create_progress_invoice, send_invoice, record_invoice_payment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/housecall-pro-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=housecall-pro, requests Housecall Pro in the Cotlet console and creates an API key there.
2. The user signs in to Housecall Pro once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Housecall Pro for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Housecall Pro server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Housecall Pro MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Housecall Pro in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Housecall Pro only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Housecall Pro login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Housecall Pro's terms; Cotlet is not affiliated with Housecall Pro.
```

## What can an AI agent do in Housecall Pro?

Cotlet is best for home-service owners and office managers on Housecall Pro who want their AI agent to draft estimates, send and chase invoices and record payments without running or fixing a server.

- **[Send estimates with good, better, best options](https://cotlet.dev/integrations/housecall-pro-api-mcp-server/send-multi-option-estimates.md)**: "Create an estimate for Dana Whitfield at 14 Elm Street for a water heater replacement with three options: a 40-gallon tank at $2,400, a 50-gallon tank at $3,100 and a tankless unit at $3,900. Show me the draft before you send it." → `list_customers`, `list_price_book`, `create_estimate`, `add_estimate_option`, `send_estimate`
- **[Chase past-due invoices](https://cotlet.dev/integrations/housecall-pro-api-mcp-server/chase-past-due-invoices.md)** (runs: weekly): "Every Monday, list Housecall Pro invoices that are past due. Skip customers tagged Service Plan, and send each of the rest a short reminder by email. Show me the list before you send anything." → `list_invoices`, `get_invoice`, `send_invoice`
- **[Bill a long job in stages](https://cotlet.dev/integrations/housecall-pro-api-mcp-server/bill-jobs-in-stages.md)** (runs: weekly): "For the Harper kitchen remodel job, create a progress invoice for 30 percent of the total, due in 14 days, and show it to me before it is sent to the customer." → `get_job`, `list_invoices`, `create_progress_invoice`, `send_invoice`
- **Create jobs from inbound requests** (runs: daily): "Read the new service requests in this inbox, add each person as a Housecall Pro customer if they are not one yet, and create a job with the service they asked for, unscheduled." → `list_customers`, `create_customer`, `create_job`
- **Record payments and close invoices**: "Match this week's checks and cash receipts to open Housecall Pro invoices and record each payment without sending a receipt until I say so." → `list_invoices`, `get_invoice`, `record_invoice_payment`

## Can Housecall Pro automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Housecall Pro connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to chase past-due invoices, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/housecall-pro/invoices. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/housecall-pro/invoices with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Housecall Pro.

### list_customers

Search customers by name, email, phone or address, with their service addresses. Access: read. REST: `GET /api/v1/housecall-pro/customers`. MCP: `housecall_pro_read → list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, email, phone number or address to search for. |
| `tag` | string | no | Only customers with this tag. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns customer profiles that match the query, as the customer search on a new job does: name, email, phone numbers and each service address. Mobile numbers are marked, because only a number in the Mobile field can receive texts. Pages hold up to 50 customers; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "customers": [
    {
      "customer_id": "cus_4f2a91",
      "name": "Dana Whitfield",
      "email": "dana@example.com",
      "mobile": "+1 555 010 0142",
      "addresses": [
        {
          "address_id": "adr_71c0",
          "street": "14 Elm Street",
          "city": "Springfield",
          "state": "IL",
          "zip": "62704"
        }
      ],
      "tags": [
        "Service Plan"
      ]
    }
  ],
  "next_cursor": null
}
```

### list_jobs

Jobs with customer, schedule, assigned team and total, newest first. Access: read. REST: `GET /api/v1/housecall-pro/jobs`. MCP: `housecall_pro_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | no | Only jobs for this customer. |
| `scheduled_from` | date | no | Only jobs scheduled on or after this date. |
| `scheduled_to` | date | no | Only jobs scheduled on or before this date. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists jobs newest first, with the customer, the service address, the scheduled start, the assigned team members and the job total. Filter by customer or by scheduled date to see what is booked. Line items and invoices come from get_job. Pages hold up to 50 jobs.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "job_91d3a7",
      "customer": {
        "customer_id": "cus_c710e3",
        "name": "Elise Harper"
      },
      "address": "8 Orchard Lane, Springfield, IL",
      "description": "Kitchen remodel",
      "scheduled_start": "2026-10-19T08:00:00-05:00",
      "team": [
        "Mike Torres"
      ],
      "total": 8400
    }
  ],
  "next_cursor": null
}
```

### get_job

One job with line items, total, notes, schedule and every invoice on it. Access: read. REST: `GET /api/v1/housecall-pro/jobs/{job_id}`. MCP: `housecall_pro_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |

Returns one job as the Job details page shows it: customer, service address, line items with prices, notes, schedule and dispatched team. It lists each invoice on the job with its status and amount, so you can see how much of the total is invoiced. Use it before creating a progress invoice.

Example response:

```json
{
  "job_id": "job_91d3a7",
  "customer": {
    "customer_id": "cus_c710e3",
    "name": "Elise Harper"
  },
  "line_items": [
    {
      "name": "Cabinet install",
      "quantity": 1,
      "unit_price": 5200
    },
    {
      "name": "Countertop, quartz",
      "quantity": 1,
      "unit_price": 3200
    }
  ],
  "total": 8400,
  "invoiced_total": 0,
  "invoices": [],
  "progress_invoicing": true
}
```

### list_estimates

Estimates with their options, totals and status such as Customer Approved or Customer Declined. Access: read. REST: `GET /api/v1/housecall-pro/estimates`. MCP: `housecall_pro_read → list_estimates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | no | Only estimates for this customer. |
| `status` | string | no | Estimate status as shown in Housecall Pro, for example Customer Approved or Customer Declined. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists estimates newest first, each with its options and the total of every option. Status is the one Housecall Pro shows, for example Customer Approved or Customer Declined. Filter by customer or by status to find estimates that still wait for an answer. Pages hold up to 50 estimates.

Example response:

```json
{
  "estimates": [
    {
      "estimate_id": "est_8e41c2",
      "customer": {
        "customer_id": "cus_4f2a91",
        "name": "Dana Whitfield"
      },
      "status": "sent",
      "customer_can_approve": "one",
      "options": [
        {
          "option_id": "opt_1",
          "name": "40-gallon tank",
          "total": 2400
        },
        {
          "option_id": "opt_2",
          "name": "50-gallon tank",
          "total": 3100
        }
      ],
      "sent_at": "2026-10-13T16:40:00-05:00"
    }
  ],
  "next_cursor": null
}
```

### list_invoices

Invoices with status, amount due, due date and last send date, filtered like the Invoice list. Access: read. REST: `GET /api/v1/housecall-pro/invoices`. MCP: `housecall_pro_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | open, paid, pending, canceled or voided. |
| `filter` | enum | no | all, unsent, due or past_due. Default: all. |
| `customer_id` | string | no | Only invoices for this customer. |
| `due_before` | date | no | Only invoices due before this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists invoices the way the Invoice list does. Status is Open, Paid, Pending, Canceled or Voided, and Open includes partially paid invoices. Use filter past_due for invoices not paid by their due date, or unsent for Open invoices with no send record. Pages hold up to 100 invoices.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "inv_7c20be",
      "job_id": "job_30b9f1",
      "customer": {
        "customer_id": "cus_20d8aa",
        "name": "Marcus Lee"
      },
      "status": "open",
      "amount": 780,
      "amount_due": 780,
      "due_date": "2026-10-02",
      "last_sent_at": "2026-09-18T09:12:00-05:00"
    }
  ],
  "next_cursor": null
}
```

### get_invoice

One invoice with line items, amount due, payment history and send history. Access: read. REST: `GET /api/v1/housecall-pro/invoices/{invoice_id}`. MCP: `housecall_pro_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or get_job. |

Returns one invoice as the invoice preview shows it: the lines, the amount due, each payment applied with its method and date, and when the invoice was last sent. A payment that has not reached the bank, such as an ACH payment, appears with pending status. Use it before resending or recording a payment.

Example response:

```json
{
  "invoice_id": "inv_7c20be",
  "job_id": "job_30b9f1",
  "status": "open",
  "line_items": [
    {
      "name": "Drain cleaning, kitchen",
      "quantity": 1,
      "unit_price": 780
    }
  ],
  "amount": 780,
  "amount_due": 780,
  "due_date": "2026-10-02",
  "payments": [],
  "sent": [
    {
      "sent_at": "2026-09-18T09:12:00-05:00",
      "channel": "email"
    }
  ],
  "online_payment_enabled": true
}
```

### list_price_book

Services and materials from your Price book with their prices. Access: read. REST: `GET /api/v1/housecall-pro/price-books`. MCP: `housecall_pro_read → list_price_book`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the item name. |
| `kind` | enum | no | service or material. Default: both. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the services and materials in your Price book with names and prices, so a new estimate or job uses the prices you already set. Search by name. Using an item on a job or estimate does not change the Price book itself. Pages hold up to 100 items.

Example response:

```json
{
  "items": [
    {
      "price_book_id": "pb_5521",
      "kind": "service",
      "name": "Water heater install, 40-gallon",
      "price": 2400
    },
    {
      "price_book_id": "pb_5530",
      "kind": "material",
      "name": "Expansion tank",
      "price": 85
    }
  ],
  "next_cursor": null
}
```

### create_customer

Add a customer with a name, contact details and a service address. Access: write, asks the user first. REST: `POST /api/v1/housecall-pro/customers`. MCP: `housecall_pro_write → create_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | First name. |
| `last_name` | string | no | Last name. |
| `email` | string | no | Email address. |
| `mobile` | string | no | Mobile number, the one that can receive texts. |
| `street` | string | no | Service address street. |
| `city` | string | no | Service address city. |
| `state` | string | no | Service address state. |
| `zip` | string | no | Service address zip code. |

Creates a customer profile with name, email, phone numbers and one service address. Run list_customers first so you do not add a second profile for someone who already exists. Put a number in mobile if you will text the customer later, because home and work numbers cannot receive texts. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "customer_id": "cus_4f2a91",
  "name": "Dana Whitfield",
  "address_id": "adr_71c0",
  "status": "created"
}
```

### create_job

Create a job for a customer with line items and, optionally, a schedule and a dispatched team member. Access: write, asks the user first. REST: `POST /api/v1/housecall-pro/customers/{customer_id}/jobs`. MCP: `housecall_pro_write → create_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer ID from list_customers. |
| `address_id` | string | no | Service address from list_customers. Default: the first address. |
| `line_items` | object[] | yes | Lines to add: name, quantity and unit_price, or price_book_id from list_price_book. A line that names a price book item uses its price unless you set unit_price. |
| `notes` | string | no | Job notes. |
| `scheduled_start` | datetime | no | Start time. Needs team_member_ids. |
| `team_member_ids` | string[] | no | Team members to dispatch. Required when scheduled_start is set. |

Creates a job for a customer and an address with service line items, notes and tags. Leave schedule out to save it unscheduled. When you schedule it, you must also dispatch at least one team member, the same rule as the New Job page. The call returns the job and the invoice that goes with it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "job_91d3a7",
  "customer_id": "cus_c710e3",
  "status": "unscheduled",
  "total": 8400,
  "invoice_id": "inv_4b2e00"
}
```

### create_estimate

Create a draft estimate for a customer with a first option and its line items. Access: write, asks the user first. REST: `POST /api/v1/housecall-pro/customers/{customer_id}/estimates`. MCP: `housecall_pro_write → create_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | string | yes | Customer ID from list_customers. |
| `address_id` | string | no | Service address from list_customers. Default: the first address. |
| `option_name` | string | no | Name of the first option, for example 'Good'. |
| `line_items` | object[] | yes | Lines to add: name, quantity and unit_price, or price_book_id from list_price_book. A line that names a price book item uses its price unless you set unit_price. |
| `customer_can_approve` | enum | no | one or several options. Default: one. |
| `scheduled_start` | datetime | no | Schedule the estimate visit. |
| `notify_customer` | boolean | no | Default: the customer profile's notification settings. |

Saves a draft estimate for a customer and address with a first option and its lines; use add_estimate_option for further tiers. The estimate is not sent. If you schedule it, the customer is notified as their profile settings say unless notify_customer is false. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "estimate_id": "est_8e41c2",
  "status": "draft",
  "options": [
    {
      "option_id": "opt_1",
      "name": "40-gallon tank",
      "total": 2400
    }
  ],
  "customer_can_approve": "one"
}
```

### add_estimate_option

Add a named option with its own line items to a draft estimate. Access: write. REST: `POST /api/v1/housecall-pro/estimates/{estimate_id}/option`. MCP: `housecall_pro_write → add_estimate_option`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `estimate_id` | string | yes | Estimate ID from list_estimates or create_estimate. |
| `name` | string | yes | Option name, for example 'Better'. |
| `line_items` | object[] | yes | Lines to add: name, quantity and unit_price, or price_book_id from list_price_book. A line that names a price book item uses its price unless you set unit_price. |

Adds one option, with its own line items and total, to an estimate, the same as + New option on the Estimate details page. It reaches no one: the option stays on the estimate until send_estimate runs. Remove an option in Housecall Pro from the three-dot menu on its tab, Delete. add_estimate_option runs without asking first for that reason.

Example response:

```json
{
  "estimate_id": "est_8e41c2",
  "option_id": "opt_3",
  "name": "Tankless unit",
  "line_items": [
    {
      "name": "Tankless water heater, installed",
      "quantity": 1,
      "unit_price": 3900
    }
  ],
  "total": 3900
}
```

### send_estimate

Send an estimate with chosen options to the customer by email or text. Access: write, asks the user first. REST: `POST /api/v1/housecall-pro/estimates/{estimate_id}`. MCP: `housecall_pro_write → send_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `estimate_id` | string | yes | Estimate ID from list_estimates or create_estimate. |
| `channels` | string[] | no | email, text or both. Default: ['email']. Text needs texting enabled on the account and a number in the customer's Mobile field. |
| `option_ids` | string[] | no | Options to include. Default: all. |
| `to` | string[] | no | Extra email addresses. Default: the customer's email. |
| `subject` | string | no | Email subject. Default: your Housecall Pro default. |
| `message` | string | no | Message to the customer. |

Sends the estimate to the customer by email, text or both, with the options you pick and an optional subject and message. Several email addresses are allowed. When the customer approves or declines, the status in Housecall Pro becomes Customer Approved or Customer Declined, and an approval asks for an e-signature. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "estimate_id": "est_8e41c2",
  "status": "sent",
  "sent_to": [
    "dana@example.com"
  ],
  "channels": [
    "email"
  ],
  "options_sent": [
    "opt_1",
    "opt_2",
    "opt_3"
  ]
}
```

### create_progress_invoice

Create an invoice for a percent or a fixed amount of a job total. Needs Progressive invoicing on the account. Access: write, asks the user first. REST: `POST /api/v1/housecall-pro/jobs/{job_id}/progress-invoices`. MCP: `housecall_pro_write → create_progress_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |
| `percent` | number | no | Share of the job total, 1 to 100. Give percent or amount. |
| `amount` | number | no | Fixed amount instead of a percent. |
| `due_in_days` | integer | no | Days from today until the invoice is due. |

Creates one invoice on a job for a percent or a fixed amount of its total, with its own due date. It needs Progressive invoicing switched on in Settings and a job created after that, and the total invoiced cannot pass 100 percent. The amount and due date cannot be edited afterwards; void and re-invoice instead. The invoice is not sent. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_4b2e8d",
  "job_id": "job_91d3a7",
  "status": "open",
  "amount": 2520,
  "percent": 30,
  "due_date": "2026-10-28",
  "invoiced_total": 2520,
  "left_to_bill": 5880
}
```

### send_invoice

Send or resend an invoice to the customer by email or text with a message. Access: write, asks the user first. REST: `POST /api/v1/housecall-pro/invoices/{invoice_id}`. MCP: `housecall_pro_write → send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or get_job. |
| `channels` | string[] | no | email, text or both. Default: ['email']. Text needs texting enabled on the account and a number in the customer's Mobile field. |
| `to` | string[] | no | Extra email addresses. Default: the customer's email. |
| `subject` | string | no | Email subject. |
| `message` | string | no | Message to the customer. |

Sends an invoice by email, text or both, with a custom subject and message, to the customer or to extra email addresses. Text needs online payments enabled on the invoice and a number in the Mobile field. Resending an invoice restarts the automatic reminder cadence. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_7c20be",
  "status": "sent",
  "sent_to": [
    "marcus@example.com"
  ],
  "channels": [
    "email"
  ],
  "sent_at": "2026-10-14T09:30:00-05:00"
}
```

### record_invoice_payment

Apply a payment to an open invoice, optionally sending the customer a receipt. Access: write, asks the user first. REST: `POST /api/v1/housecall-pro/invoices/{invoice_id}/payment`. MCP: `housecall_pro_write → record_invoice_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or get_job. |
| `amount` | number | yes | Amount paid. |
| `method` | string | yes | Payment method as listed in the Pay window, for example check or cash. |
| `notify_customer` | boolean | no | Email a receipt. Default: false. A card on file always sends one. |
| `receipt_email` | string | no | Address for the receipt. |

Applies a payment to one invoice, the same as Pay in the invoice preview: amount, payment method and an optional receipt email. A partial payment is allowed unless Progress Invoicing is on, and then the full amount is required. A card on file is used automatically and always notifies the customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_7c20be",
  "payment_id": "pay_2c91",
  "amount": 780,
  "method": "check",
  "status": "paid",
  "receipt_sent": false
}
```

## How do I connect Housecall Pro to Claude Code, Codex or Cursor?

Connecting Housecall Pro takes three steps: sign up, sign in to Housecall Pro once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Housecall Pro to your agent.

1. **Create an account** Sign up and add Housecall Pro in the console. Your API key is there too.

2. **Sign in to Housecall Pro in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Housecall Pro there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Housecall Pro tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Create an estimate for Dana Whitfield at 14 Elm Street for a water heater replacement with three options: a 40-gallon tank at $2,400, a 50-gallon tank at $3,100 and a tankless unit at $3,900. Show me the draft before you send it.
```

### Call Housecall Pro from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/housecall-pro with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/housecall-pro/invoices/inv_7c20be \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"channels":["email"],"subject":"Reminder: invoice for your water heater service","message":"Hi Marcus, the balance of $780.00 was due on 2 October. You can pay online from the invoice. Thank you."}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "invoice_id": "inv_7c20be",
  "status": "sent",
  "sent_to": [
    "marcus@example.com"
  ],
  "channels": [
    "email"
  ],
  "sent_at": "2026-10-14T09:30:00-05:00"
}
```

## Why use Cotlet for Housecall Pro?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Housecall Pro yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Housecall Pro changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Housecall Pro to Cotlet?

Yes. You sign in to Housecall Pro yourself, in your own Cloud Browser, and we never save your password. Your agents only get Housecall Pro once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Housecall Pro integration?**

No, Cotlet is independent of Housecall Pro. Housecall Pro's own API comes only with a paid plan. Cotlet works through your own Housecall Pro account, the way you use Housecall Pro in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Housecall Pro in your console: your agents lose access at once and you stay signed in. Signing out of Housecall Pro in the browser works too, and Reset browser deletes the whole profile.

## Is there a Housecall Pro MCP server on GitHub?

Yes. Open-source Housecall Pro MCP servers exist on GitHub, usually maintained by one person. They call the official REST API, so they need the MAX plan and your own API key, you install and update them yourself, and they cannot send or pay an invoice because the API has no such call. Cotlet hosts the same kind of server for you, signs in to the app as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone or install it, generate an API key as an admin, add it to each MCP client | Sign up, sign in to Housecall Pro once, add one MCP server or API key |
| Plan needed | MAX plan for the API key | Works in your own account on the plan you have |
| When Housecall Pro changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Housecall Pro access | A key in a file on your computer; an admin key reaches the whole account | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | The key stays valid until you delete it | Your Cloud Browser keeps you signed in; if Housecall Pro logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Housecall Pro changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Housecall Pro API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Housecall Pro API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Housecall Pro account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Housecall Pro yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Housecall Pro only after you enable it. When Housecall Pro signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Housecall Pro, sign out of Housecall Pro in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Housecall Pro's terms:** You use your own Housecall Pro account and stay responsible for following Housecall Pro's terms. Cotlet is independent and not affiliated with Housecall Pro. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Housecall Pro in the console and press Request access. Then you create your API key and connect Housecall Pro there.

**Do I need to be technical?**

No. You sign in to Housecall Pro once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Housecall Pro to Cotlet?**

Yes. You sign in to Housecall Pro yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Housecall Pro once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Housecall Pro sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Housecall Pro cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Housecall Pro's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Housecall Pro sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Housecall Pro login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Housecall Pro offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need the MAX plan to use Cotlet with Housecall Pro?**

No. Housecall Pro gives its API key only to MAX plan pros, with limited access. Cotlet signs in to your own account instead, so it does not use that key. What your agent can do still follows your role in Housecall Pro, and Progressive invoicing must be on for progress invoices.

**Can my agent send or pay an invoice, which the API cannot?**

Yes. send_invoice and record_invoice_payment work like Send and Pay in the web portal. Both reach your customers or your books, so you confirm each call by default. Texting also needs text messaging approved on your account and a number in the customer's Mobile field.

**Can my agent post or send messages in Housecall Pro without asking me?**

No. Every call to create_customer, create_job, create_estimate, send_estimate, create_progress_invoice, send_invoice or record_invoice_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_estimate_option runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Housecall Pro API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/housecall-pro from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.