# Houzz Scraper - Home Improvement Professionals (`goat255/houzz-scraper`) Actor

Collect home improvement professionals by trade and location. One clean row per business with phone, full postal address, areas served, social profiles and website. No login and no API key.

- **URL**: https://apify.com/goat255/houzz-scraper.md
- **Developed by:** [Goutam Soni](https://apify.com/goat255) (community)
- **Categories:** Business, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.20 / 1,000 professional scrapeds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Houzz Scraper

Collect home improvement professionals by trade and location. One clean row per business with phone, full postal address, areas served, social profiles and website. No login and no API key.

### What it does

- **Contact details ready to use.** Phone number as displayed, plus a digits-only version for joining and deduplication.
- **Full postal address split into fields**: street, city, state, ZIP and country, plus one combined line.
- **Website and listing page kept apart.** A business's page in the directory is not their own website, so it is returned separately as `profileUrl` and never passed off as one.
- **Social profiles** as their own list, separate from any other links.
- **Deduplicated across every trade and location**, so a business listed under two searches is delivered once and charged once.
- **Many trades and locations in one run**, all returning the same fields.

Common uses: lead lists for suppliers and software vendors, local market research, competitor mapping, recruitment, and building a trades directory.

### Input

| Field | Type | Description |
|---|---|---|
| `trades` | array | Trade slugs as they appear in the site address. See the list below. |
| `locations` | array | Locations in the site's own form, for example `Austin--TX`. |
| `maxResultsPerSearch` | integer | Cap per trade and location pair. Default 100. |
| `proxyConfiguration` | object | Optional. Enable to spread requests across IPs. |

Trades confirmed to work: `general-contractor`, `architect`, `interior-designer`, `landscape-architect`, `roofing-and-gutters`, `painter`, `plumber`, `electrician`. Others may exist; a trade that is not recognised is reported in the log and skipped rather than returning unrelated results.

#### Example input

```json
{
  "trades": ["general-contractor", "architect"],
  "locations": ["Austin--TX", "New-York--NY"],
  "maxResultsPerSearch": 300
}
```

### Output

Each item is one professional.

```json
{
  "name": "Acme Design & Build",
  "trade": "general-contractor",
  "phone": "+1 555-0100",
  "phoneDigits": "15550100",
  "website": "https://example.com",
  "profileUrl": "https://www.houzz.com/professionals/general-contractors/example-pf~1000000000",
  "street": "1 Example Street",
  "city": "Austin",
  "region": "TX",
  "postalCode": "78701",
  "country": "US",
  "address": "1 Example Street, Austin, TX, 78701",
  "areaServed": "Austin",
  "searchLocation": "Austin--TX",
  "socialProfiles": ["https://www.facebook.com/example"],
  "otherLinks": [],
  "imageUrl": "https://example.com/photo.jpg"
}
```

### Notes

- **The listing reorders between requests.** Asking for the same page twice does not return quite the same set, so this actor does not assume a fixed number of pages. It keeps requesting until several consecutive requests turn up nothing new, and deduplicates as it goes. That is why the run log shows more requests than a simple page count would suggest.
- Because of that reordering, a second run of the same search can surface a few businesses the first run did not. Raising `maxResultsPerSearch` gives the run more room to find them.
- `website` is filled only when a business publishes its own address. Many list only social profiles, so this field is often `null` while `profileUrl` is always present.
- Some entries list a bare social handle rather than a full address. The platform cannot be determined from a handle alone, so those are left out instead of being filed under a guess.
- `street` is missing for a minority of businesses that do not publish one. Those rows keep every other field.
- Results for a location include nearby areas, so a search can return businesses in neighbouring states. The `region` field shows exactly where each one is.

### Privacy

To improve our actors we collect anonymized usage telemetry (run stats and input patterns). No personal account data is collected.

# Actor input Schema

## `trades` (type: `array`):

Trade categories to collect. Use the exact slug as it appears in the site address, for example general-contractor. Unrecognised trades are reported and skipped rather than returning unrelated results.

## `locations` (type: `array`):

Locations to search, in the site's own form, for example New-York--NY or Austin--TX.

## `maxResultsPerSearch` (type: `integer`):

Cap for each trade and location pair. Results are deduplicated across every pair.

## `proxyConfiguration` (type: `object`):

Optional. Enable to spread requests across IPs.

## Actor input object example

```json
{
  "trades": [
    "general-contractor"
  ],
  "locations": [
    "Austin--TX"
  ],
  "maxResultsPerSearch": 100
}
```

# Actor output Schema

## `records` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "trades": [
        "general-contractor"
    ],
    "locations": [
        "Austin--TX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("goat255/houzz-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "trades": ["general-contractor"],
    "locations": ["Austin--TX"],
}

# Run the Actor and wait for it to finish
run = client.actor("goat255/houzz-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "trades": [
    "general-contractor"
  ],
  "locations": [
    "Austin--TX"
  ]
}' |
apify call goat255/houzz-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=goat255/houzz-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/AIXvNA0VTg0sRNG8j/builds/MYZZDviNxWJcKHBGo/openapi.json