# Houzz Pro Directory Finder by City & Category (`dataspryva/houzz-pro-directory-finder-by-city-and-category`) Actor

Find Houzz contractors, architects, and designers by city and category across 16 countries, with ratings, reviews, hires, services, license status, and location for each professional.

- **URL**: https://apify.com/dataspryva/houzz-pro-directory-finder-by-city-and-category.md
- **Developed by:** [Dataspryva](https://apify.com/dataspryva) (community)
- **Categories:** Lead generation, Real estate, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.49 / 1,000 results

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Houzz Professionals, Reviews & Photos Scraper

Scrape **Houzz** professional directories across 15 country sites, open each pro's profile for contact, service, award, social and licensing detail, pull their full review history, and browse the photo inspiration library by room, style or keyword. Everything is public and cookieless: no Houzz account, browser, API key or proxy setup is needed.

### What this actor does

- **Five modes:** `search`, `byUrls`, `profiles`, `reviews`, `photos`
- **Every live market:** US, Canada, UK, Ireland, Australia, New Zealand, Germany, France, Italy, Spain, India, Singapore, Japan, Denmark and Sweden, with localised profile paths
- **Search by city + profession or keyword**, with rating and review-count filters and server-side sort
- **Deep directory pagination:** up to 100 pages per category and 30 pages for keyword-filtered searches
- **Rich profiles:** business name, contact person, phone, website, full address, services, awards, badges, credentials, social links, licence status, project/photo/follower counts and review aspect scores
- **Full reviews:** reviewer, rating, body, project date and price, review photos and the professional's reply
- **Photo inspiration:** room category, keyword, 19 design styles, optional detail enrichment for full image sets, owner and location
- **Optional email enrichment** from each professional's own website
- Empty fields are omitted from every record instead of being returned as null

### Output per professional

- `title`, `businessName`, `description`
- `phoneNumber`, `websiteUrl`, `contactName`, `contactEmail`, `emails[]`, `emailSourceUrl`
- `licenseNumber`, `licenseType`, `licenseVerifiedDate`, `licenseIssuedBy`, `verifiedLicense`
- `ratingValue`, `reviewCount`, `hiresOnHouzz`, `followersCount`, `projectCount`, `photoCount`, `galleryCount`
- `isProVerified`, `isPaidPro`, `reviewAspectRatings{workQuality, communication, onTime, value}`
- `servicesProvided[]`, `awards[]`, `badges[]`, `credentials[]`, `faq[]`
- `socialLinks{facebook, instagram, twitter, pinterest, youtube, linkedin, tiktok}`
- `proId`, `userId`, `userName`, `category`, `categories[]`
- `streetAddress`, `city`, `state`, `postalCode`, `country`, `countryCode`, `fullAddress`
- `latitude`, `longitude`, `areaServed[]`, `imageUrl`
- `reviews[]`, `reviewsFetched`, `reviewsTotalAvailable` when reviews are requested
- `sourceUrl`, `profileUrl`, `canonicalUrl`, `slug`
- `siteName`, `recordType: "professional"`, `recordSource`, `scrapedAt`

### Output per review

- `reviewId`, `proId`, `proName`, `profileUrl`
- `rating`, `body`, `relationship`, `projectDate`, `projectPrice`
- `reviewerName`, `reviewerUserName`, `reviewerProfileUrl`, `reviewerIsPro`
- `createdAt`, `numberOfLikes`, `photos[]`
- `proResponse`, `proResponseAt`
- `recordType: "review"`, `scrapedAt`

### Output per photo

- `photoId`, `title`, `description`, `url`, `canonicalUrl`
- `imageUrl`, `heroImageUrl`, `images[]`, `imageWidth`, `imageHeight`
- `categoryId`, `category`, `styleId`, `style`
- `ownerId`, `ownerName`, `ownerProfileUrl`, `ownerIsPro`
- `projectId`, `questionCount`, `comments`, `recentBuzz`
- `metroArea`, `city`, `state`, `countryCode`
- `isFeatured`, `isGated`, `sourceUrl`
- `recordType: "photo"`, `scrapedAt`

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `mode` | string | `search` | `search` / `byUrls` / `profiles` / `reviews` / `photos` |
| `country` | string | `us` | Houzz market: `us`, `ca`, `uk`, `ie`, `au`, `nz`, `de`, `fr`, `it`, `es`, `in`, `sg`, `jp`, `dk`, `se`; legacy `ru` is accepted for saved tasks but Houzz Russia is offline |
| `city` | string | `Los Angeles, CA` | City or city + state for search mode |
| `profession` | string | `general-contractor` | 16 universal professions mapped to each market |
| `categorySlug` | string | – | Exact Houzz category slug override |
| `keyword` | string | – | Professional keyword filter or photo search term |
| `sortBy` | string | `relevance` | `relevance` / `reviews` / `rating` / `distance` |
| `minRating` | number | `0` | Drop professionals below this rating |
| `minReviewCount` | integer | `0` | Drop professionals below this review count |
| `directoryUrls` | array | `[]` | Houzz directory, category or search-result URLs |
| `profileUrls` | array | `[]` | Direct Houzz professional profile URLs |
| `photoUrls` | array | `[]` | Direct Houzz photo detail URLs |
| `photoCategory` | string | `kitchen` | Room category for photo browsing |
| `photoStyle` | string | – | Optional design style filter |
| `includeReviews` | boolean | `false` | Attach review history to professional records |
| `maxReviewsPerPro` | integer | `20` | Review cap per professional; `0` means all |
| `fetchDetails` | boolean | `true` | Open each professional profile |
| `fetchPhotoDetails` | boolean | `false` | Open each photo for full image and owner detail |
| `enrichEmails` | boolean | `false` | Best-effort email lookup on the pro's own website |
| `maxItems` | integer | `25` | Hard record cap (1–5,000) |
| `maxPages` | integer | `0` | Optional page cap; `0` uses the source ceiling |

#### Example: contractors in Los Angeles

```json
{
  "mode": "search",
  "country": "us",
  "city": "Los Angeles, CA",
  "profession": "general-contractor",
  "minRating": 4.5,
  "minReviewCount": 10,
  "maxItems": 100
}
```

#### Example: London interior designers with reviews

```json
{
  "mode": "search",
  "country": "uk",
  "city": "London",
  "profession": "interior-designer",
  "includeReviews": true,
  "maxReviewsPerPro": 50,
  "maxItems": 40
}
```

#### Example: specific profiles and directory URLs

```json
{
  "mode": "byUrls",
  "directoryUrls": [
    "https://www.houzz.de/professionals/architekten/berlin-16-de-probr0-bo~t_11973~r_2950159"
  ],
  "profileUrls": [
    "https://www.houzz.com/professionals/general-contractors/goldenline-remodeling-pfvwus-pf~28977151"
  ],
  "fetchDetails": true,
  "maxItems": 30
}
```

#### Example: kitchen photo inspiration

```json
{
  "mode": "photos",
  "photoCategory": "kitchen",
  "photoStyle": "scandinavian",
  "fetchPhotoDetails": true,
  "maxItems": 60
}
```

### Use cases

- **Contractor lead generation** — build a city list with phone, website, address, licence and review proof
- **Competitive benchmarking** — compare services, awards and review scores across firms in one category
- **Market expansion research** — compare the same profession across 15 Houzz country sites
- **Vendor due diligence** — check credentials, licence status, project volume and owner replies
- **Review intelligence** — export reviewer sentiment, project budgets and response behaviour
- **Design trend research** — collect photo records by room, style and metro area for moodboards or analysis

### FAQ

**Is this affiliated with Houzz?**
No. This is an independent third-party actor that reads publicly visible Houzz pages. It is not operated by or affiliated with Houzz.

**Do I need a Houzz account, cookies or an API key?**
No. Every supported mode works anonymously on public pages. There is no login step.

**Do I need to configure a proxy?**
No. The actor makes direct requests and does not require proxy setup. Just choose a mode and run it.

**Why does Houzz Japan sometimes return no professionals?**
Houzz Japan intermittently blocks datacenter IPs or serves 404 profile pages. The actor reports the failed fetch and keeps any directory cards it already parsed instead of inventing rows. Other 14 markets run directly.

**Why do some records have fewer fields than others?**
Professionals publish different amounts of information, and some categories show fewer badges or services. Fields with no value on the source page are omitted, never returned as null.

**How many professionals can one search return?**
A category or city directory serves up to 100 pages, and a keyword-filtered search stops at 30 pages. Coverage also depends on how many professionals are actually active in that city and profession.

**Why is `phoneNumber` sometimes a toll-free number?**
Houzz may display a business tracking number on the profile while the directory card shows a local number. The actor prefers the local directory number when both are available.

**Why do photo keyword searches stop before a room browse does?**
Houzz caps photo keyword results at 200 items (10 pages), while room browsing goes much deeper. The actor reports the ceiling instead of silently returning fewer photos.

**Why is there no product mode?**
Shop Houzz closed in 2026. The product pages now show "No Longer Available" or return 404, so there is no live product data to scrape. Professional and photo data are unaffected.

**Can I combine several inputs in one run?**
Yes. Directory URLs and profile URLs can be mixed, and `search` accepts a city plus profession while also honouring any direct URLs you add.

# Actor input Schema

## `mode` (type: `string`):

What to scrape. `search` builds a directory from country + city + profession; `byUrls` reads directory URLs; `profiles` reads profile URLs; `reviews` emits review rows; `photos` browses photo inspiration.

## `country` (type: `string`):

Houzz market used for search and profile URLs.

## `city` (type: `string`):

City or city + state to search, e.g. `Los Angeles, CA`, `London`, `Berlin`. Used with profession or categorySlug in search mode.

## `profession` (type: `string`):

Universal profession mapped to the selected market's Houzz category. Used in search mode.

## `categorySlug` (type: `string`):

Exact Houzz category slug, used instead of the mapped profession, e.g. `general-contractor`, `architekten`, `architectes`. Use a direct directory URL if you are unsure.

## `keyword` (type: `string`):

Optional keyword filter for professional search, or the search term for photo mode.

## `sortBy` (type: `string`):

Server-side order for professional directory results.

## `minRating` (type: `number`):

Drop professionals below this star rating. Set 0 to keep all.

## `minReviewCount` (type: `integer`):

Drop professionals with fewer reviews. Set 0 to keep all.

## `directoryUrls` (type: `array`):

Houzz professional directory, category or search-result URLs. All live markets and localised paths are accepted.

## `profileUrls` (type: `array`):

Direct Houzz professional profile URLs, including localised paths such as /experten/, /professionnels/ and /profesionales/.

## `photoUrls` (type: `array`):

Direct Houzz photo detail URLs. Use mode=photos.

## `photoCategory` (type: `string`):

Room category for photo inspiration browsing. Use keyword to search instead.

## `photoStyle` (type: `string`):

Optional design style filter for photo inspiration.

## `includeReviews` (type: `boolean`):

Attach review history to each professional record.

## `maxReviewsPerPro` (type: `integer`):

Review cap per professional. Set 0 to fetch the full history (up to 1,024).

## `fetchDetails` (type: `boolean`):

Open each professional profile for services, awards, socials, counts and licensing. Turn off for directory-card-only records.

## `fetchPhotoDetails` (type: `boolean`):

Open each photo for full image sizes, owner, location and question count.

## `enrichEmails` (type: `boolean`):

Best-effort email lookup on each professional's own website. Adds requests and is optional.

## `maxItems` (type: `integer`):

Hard cap on emitted records.

## `maxPages` (type: `integer`):

Optional page cap. Set 0 to use the source ceiling: 100 directory pages, 30 keyword pages, 250 photo pages or 10 photo keyword pages.

## Actor input object example

```json
{
  "mode": "search",
  "country": "us",
  "city": "Los Angeles, CA",
  "profession": "general-contractor",
  "categorySlug": "",
  "keyword": "",
  "sortBy": "relevance",
  "minRating": 0,
  "minReviewCount": 0,
  "directoryUrls": [],
  "profileUrls": [],
  "photoUrls": [],
  "photoCategory": "kitchen",
  "photoStyle": "",
  "includeReviews": false,
  "maxReviewsPerPro": 20,
  "fetchDetails": true,
  "fetchPhotoDetails": false,
  "enrichEmails": false,
  "maxItems": 1,
  "maxPages": 0
}
```

# Actor output Schema

## `professionals` (type: `string`):

Dataset containing Houzz professional records with contact, service, award, social and review data.

## `reviews` (type: `string`):

Dataset containing Houzz review rows with reviewer, project and owner-response detail.

## `photos` (type: `string`):

Dataset containing Houzz photo inspiration records with room, style, owner and image detail.

# 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 = {
    "mode": "search",
    "country": "us",
    "city": "Los Angeles, CA",
    "profession": "general-contractor",
    "categorySlug": "",
    "keyword": "",
    "sortBy": "relevance",
    "minRating": 0,
    "minReviewCount": 0,
    "directoryUrls": [],
    "profileUrls": [],
    "photoUrls": [],
    "photoCategory": "kitchen",
    "photoStyle": "",
    "includeReviews": false,
    "maxReviewsPerPro": 20,
    "fetchDetails": true,
    "fetchPhotoDetails": false,
    "enrichEmails": false,
    "maxItems": 1,
    "maxPages": 0
};

// Run the Actor and wait for it to finish
const run = await client.actor("dataspryva/houzz-pro-directory-finder-by-city-and-category").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 = {
    "mode": "search",
    "country": "us",
    "city": "Los Angeles, CA",
    "profession": "general-contractor",
    "categorySlug": "",
    "keyword": "",
    "sortBy": "relevance",
    "minRating": 0,
    "minReviewCount": 0,
    "directoryUrls": [],
    "profileUrls": [],
    "photoUrls": [],
    "photoCategory": "kitchen",
    "photoStyle": "",
    "includeReviews": False,
    "maxReviewsPerPro": 20,
    "fetchDetails": True,
    "fetchPhotoDetails": False,
    "enrichEmails": False,
    "maxItems": 1,
    "maxPages": 0,
}

# Run the Actor and wait for it to finish
run = client.actor("dataspryva/houzz-pro-directory-finder-by-city-and-category").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "mode": "search",
  "country": "us",
  "city": "Los Angeles, CA",
  "profession": "general-contractor",
  "categorySlug": "",
  "keyword": "",
  "sortBy": "relevance",
  "minRating": 0,
  "minReviewCount": 0,
  "directoryUrls": [],
  "profileUrls": [],
  "photoUrls": [],
  "photoCategory": "kitchen",
  "photoStyle": "",
  "includeReviews": false,
  "maxReviewsPerPro": 20,
  "fetchDetails": true,
  "fetchPhotoDetails": false,
  "enrichEmails": false,
  "maxItems": 1,
  "maxPages": 0
}' |
apify call dataspryva/houzz-pro-directory-finder-by-city-and-category --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/houzz-pro-directory-finder-by-city-and-category"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

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