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

> Houzz provisions Houzz Pro API accounts itself, with no self-serve sign-up yet. 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/houzz-pro

Houzz Pro has an API with service accounts that Houzz provisions, and no self-serve sign-up yet (checked 19 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Houzz 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 Houzz Pro session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=houzz-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 Houzz Pro. Houzz Pro is a trademark of its owner. If Houzz 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/quiet-leads" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days": 7}'
```

Node.js

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

Response 200 OK · JSON

```
{
"data": [
{
"lead": "Jordan P.",
"project_type": "Bathroom remodel",
"phase": "New",
"last_contact": "2026-11-11",
"phone": "(555) 014-2290"
},
{
"lead": "Alex K.",
"project_type": "Kitchen refresh",
"phase": "Site visit",
"last_contact": "2026-11-10",
"phone": "(555) 018-7741"
}
]
}
```

01 Build

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

1. 01  
www.houzz.com  
Signed in  
### Sign in to Houzz Pro in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List my leads with no reply from us in the last 7 days, with the project type and phone.  
### Do the job once with your agent.  
For example: "List my leads with no reply from us in the last 7 days, with the project type and phone."
3. 03  
Save endpoint  
Name  
quiet-leads  
Input  
days  
Returns  
lead, project\_type, phase, last\_contact, phone  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a number of days or a project, and the fields it returns.
4. 04  
$ POST /api/v1/custom/quiet-leads  
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 Houzz Pro session.

02 Endpoints

## Example endpoints you could build for Houzz Pro

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

- POST `/api/v1/custom/quiet-leads`  
### Leads that went quiet  
Leads with no reply in the days you name, with phase and phone
- POST `/api/v1/custom/project-invoices`  
### Invoices of a project  
Invoice number, total, status and payments received
- POST `/api/v1/custom/open-estimates`  
### Estimates waiting on a client  
Each sent estimate with its total and the days since it went out
- POST `/api/v1/custom/crew-hours`  
### Crew hours for a week  
Hours per person and per project from time tracking
- POST `/api/v1/custom/log-time` writes  
### Log time on a project  
A time entry for a crew member on the project and date you name
- 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/quiet-leads" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"days": 7}'
```

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

Response · 200 OK

```
{
"data": [
{
"lead": "Jordan P.",
"project_type": "Bathroom remodel",
"phase": "New",
"last_contact": "2026-11-11",
"phone": "(555) 014-2290"
},
{
"lead": "Alex K.",
"project_type": "Kitchen refresh",
"phase": "Site visit",
"last_contact": "2026-11-10",
"phone": "(555) 018-7741"
}
]
}
```

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

- Schedule Cotlet endpoint Slack or email  
### A Monday follow-up list in n8n or Make.  
Leads that went quiet, sent to Slack or email with the phone number of each.
- Schedule endpoint Google Sheets  
### A cash-flow sheet.  
Unpaid invoices across your projects, pulled into Google Sheets each week.
- Friday endpoint Payroll sheet  
### Crew hours to payroll.  
Hours per person for the week, sent to your payroll sheet every Friday.
- Chat agent endpoint invoices  
### Your own AI assistant.  
A chat agent that checks a project's invoices before it answers a homeowner's question.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Houzz Pro session, so it can read and change only what your Houzz 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 logging time, 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/log-time

would POST www.houzz.com/... log 6 hours for Dan on Elm Avenue

`log-time`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Houzz Pro have an official API?

Houzz provisions Houzz Pro API service accounts itself, and there is no self-serve sign-up yet (checked 19 Nov 2026). The Houzz Pro app on Zapier creates leads and projects, one way into Houzz Pro. The full picture with sources: [Does Houzz Pro have an API or MCP server?](https://cotlet.dev/api-status/houzz-pro.md)

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

1/3

Official API

On request

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

## Houzz Pro API with Cotlet: questions

### Is this an official Houzz Pro API?

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

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