# HUD Multifamily Property Manager Leads Section 8 (`infocomp/hud-multifamily-leads`) Actor

HUD multifamily property manager leads for assisted apartments: management company, firm-level main phone, Section 8 contract expiry, REAC score and troubled/watch-list status. Filter by state, city, units, expiry. No personal names or emails. $3/1,000. Not an official HUD product.

- **URL**: https://apify.com/infocomp/hud-multifamily-leads.md
- **Developed by:** [InfoComp Data](https://apify.com/infocomp) (community)
- **Categories:** Lead generation, Business, Real estate
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 property leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## HUD Multifamily Owner/Manager Leads | Business Leads

Find **HUD-assisted apartment properties and the companies that manage them**. Each row is one property with its
**management company**, the company's **firm-level main phone**, unit counts, **Section 8 / HUD assistance contract
expiration date**, last **REAC physical-inspection score**, and HUD's **troubled / watch-list** status.

Built for people who sell to apartment operators: property-management software and services, maintenance and
renovation contractors, insurance, lenders and brokers, affordable-housing buyers, and consultants who help owners
with expiring HUD contracts or failing inspections.

> **Not an official HUD product.** Not affiliated with or endorsed by the U.S. Department of Housing and Urban
> Development (HUD) or the US government. Data comes from HUD's public "Multifamily Properties - Assisted" dataset
> (HUD Open Data). HUD gives its **date of coverage as 12/2025**; HUD last updated the dataset on **Oct 23, 2026**.
> Records can be out of date, so verify before you rely on them.

### What you get

- About **23,800** HUD-assisted multifamily properties nationwide (Texas: about 1,000).
- Property name, address, city, state, ZIP code, county, latitude and longitude, total and assisted units, property category, and population served (family, elderly, disabled).
- **Management company** name, its city and state, and how many HUD properties it manages nationwide.
- **Company main phone** (firm-level only, see below) and the property's on-site office phone.
- Main HUD assistance contract: number, program, contract count, **expiration date and months left**.
- Last REAC inspection score and date, troubled status, watch-list flag, FHA number and loan maturity date.

#### Firm-level contacts only (privacy)

This is a **company** lead list, not a list of people.

- **No personal names.** Contact persons and HUD staff are never included.
- **No emails at all.** HUD's emails are almost all individual mailboxes. Only about 1% are role inboxes such as info@, so every email is dropped.
- **No tenant or demographic data.**
- `management_company_phone` is filled only when **at least 2 different staff at that company** list the same number in HUD's data, which makes it a shared company line rather than one person's. Extensions are removed.
  - Otherwise the field is empty. About 72% of properties have one.
  - Use **Only leads with a firm-level company phone** to skip the rest for free.

### Input

| Field | Default | What it does |
|---|---|---|
| States | `["TX"]` | Two-letter codes or state names. Leave empty for all states. |
| Cities | none | Property city names. Matches the start of the name. |
| Minimum total units | none | For example 50. |
| Section 8 contract expiring within (months) | none | For example 24 finds contracts that expire in the next 2 years. |
| Max REAC inspection score | none | For example 70 finds properties that scored poorly. |
| Only troubled or watch-list properties | off | Keeps only properties HUD marks as troubled or potentially troubled, or that are on its watch list. |
| Management company contains | none | For example "National Church Residences". |
| Only leads with a firm-level company phone | off | Skips rows without a company phone, at no charge. |
| Max results | 25 | Stops after this many rows. |

The default input returns 25 Texas properties in a few seconds.

### Output sample

This row is real and untrimmed. It comes from a local default run on Nov 2, 2026.

```json
{
  "property_id": "800000075",
  "property_name": "VIRGINIA FLATS",
  "address": "2250 W Virginia St",
  "city": "Beaumont",
  "state": "TX",
  "zip_code": "77705",
  "county": "Jefferson",
  "latitude": 30.042341,
  "longitude": -94.106944,
  "total_units": 110,
  "assisted_units": 44,
  "property_category": "Subsidized - Previously Insured",
  "population_served": "Family",
  "property_office_phone": "409-842-3647",
  "management_company": "ITEX Property Management LLC",
  "management_company_phone": "409-724-0020",
  "management_company_city": "Port Arthur",
  "management_company_state": "TX",
  "management_company_hud_properties": 27,
  "reac_inspection_score": 99,
  "reac_inspection_score_raw": "99",
  "reac_inspection_date": "2024-01-31",
  "troubled_status": "Not troubled",
  "on_watch_list": false,
  "section8_contract_number": "TX24M000048",
  "assistance_program": "LMSA",
  "contract_count": 1,
  "contract_expiration_date": "2042-01-31",
  "months_to_contract_expiration": 182,
  "fha_number": null,
  "loan_maturity_date": null,
  "hud_data_coverage": "2025-12",
  "source": "U.S. Department of Housing and Urban Development (HUD), \"Multifamily Properties - Assisted\" (HUD Open Data, keyless public layer). Date of coverage: 12/2025.",
  "disclaimer": "Not an official HUD product or determination. Not affiliated with or endorsed by HUD or the US government. Provided as-is from public HUD data; verify before relying on it.",
  "hud_layer_last_edited": "2026-10-23T17:23:28+00:00",
  "retrieved_at": "2026-11-02T17:05:24Z"
}
```

The dataset has an "overview" table view and an "all fields" view. `RUN_SUMMARY` in the key-value store lists the filters, counts, free skips and HTTP stats.

### Pricing

Pay per event: **`property-lead` at $0.003 per property row = $3.00 per 1,000 leads**. There is no start fee and no run fee.

- Empty runs, failed runs and filtered-out properties are **free**, and those rows are not saved.
- The Actor respects the maximum cost you set for a run. It stops cleanly when it reaches the limit.

### How it works

The Actor reads HUD's public dataset, which needs no key or login, in pages of 2,000 records. It requests only the columns it outputs.
For each management company in your results, it also runs a single grouped lookup to find the firm's shared phone number and its number of HUD properties.
The default run uses 4 requests. In local tests, 5,000 US rows took about 8 seconds, and a full nationwide scan with filters took about 20 seconds; on the Apify cloud it takes about 55 seconds.

### Data source and terms

- Source: U.S. Department of Housing and Urban Development, "Multifamily Properties - Assisted", published on HUD Open Data (HUD's official ArcGIS open-data site).
- This is a federal government work, and HUD publishes it openly. HUD's license text is a no-warranty, no-liability disclaimer. This Actor passes that on: data is provided as-is.
- Field meanings follow HUD's data dictionary. "Troubled" and REAC scores are HUD's own classifications, not ours.
- HUD credit is on every row (`source`). The not-an-official-HUD-product notice is on every row (`disclaimer`).

### Related InfoComp tools

- [SEC Form D Leads: New Startup Private Raise Filings](https://apify.com/infocomp/form-d-funding-leads): companies that just raised private capital, from public SEC EDGAR Form D filings.
- [Colorado New Business Filings: LLC & Corp Leads](https://apify.com/infocomp/new-business-filings-colorado): newly registered Colorado LLCs, corporations and nonprofits from the State's public open data.
- [FMCSA New MC Authority Leads: Carriers & Brokers](https://apify.com/infocomp/fmcsa-new-carrier-leads): trucking companies, freight brokers and forwarders whose FMCSA operating authority was just granted.
- [FMCSA USDOT Carrier Vetting: Authority & Insurance](https://apify.com/infocomp/fmcsa-carrier-vetting): bulk-check USDOT numbers: operating authority, insurance on file, safety flags and change alerts from FMCSA public data.
- [FDA Device Establishment Leads via openFDA](https://apify.com/infocomp/fda-device-establishment-leads): medical device makers, contract manufacturers and sterilizers from FDA registration data via openFDA.
- [OIG LEIE Exclusion & Medicare Opt-Out NPI Screen](https://apify.com/infocomp/oig-exclusion-optout-screen): bulk-check NPIs against the HHS-OIG LEIE file and the CMS Medicare opt-out list.
- [SAM.gov RFP Feed: Federal Contract Opportunities](https://apify.com/infocomp/sam-gov-opportunities): US federal contract opportunities (RFPs, solicitations, awards) from official SAM.gov public data.
- [EU TED & UK Tender Feed: Find a Tender Notices](https://apify.com/infocomp/eu-uk-tenders): EU and UK public tenders in one feed, from official TED, Find a Tender and Contracts Finder APIs.
- [Greenhouse Lever Ashby SmartRecruiters Jobs API](https://apify.com/infocomp/ats-jobs-feed): live job postings from Greenhouse, Lever, Ashby and SmartRecruiters via their official job-board APIs.
- [US Address Geocoder & FEMA Flood Zone Risk API](https://apify.com/infocomp/us-address-risk-enricher): batch-geocode US addresses with the Census Bureau and add FEMA flood zone and National Risk Index ratings.
- [NHTSA Bulk VIN Decoder: Specs, Recalls & MPG](https://apify.com/infocomp/bulk-vin-decoder-recalls-mpg): decode VINs in bulk with NHTSA vPIC, plus recall campaigns and EPA fuel economy.
- [arXiv PubMed Crossref OpenAlex Paper Search](https://apify.com/infocomp/scholarly-paper-search): search arXiv, PubMed, Crossref and OpenAlex in one run via official APIs, de-duplicated by DOI.
- [CMS Home Health Hospice Dialysis Facility Leads](https://apify.com/infocomp/cms-facility-leads): Medicare-certified home health agencies, hospices and dialysis centers from CMS open data, facility-level.
- [Company Name to Website Finder: LEI & CIK](https://apify.com/infocomp/wikidata-company-finder): turn company names into official websites, HQ, employees, industry, ticker, LEI and SEC CIK from Wikidata.
- [FDA 510(k) Clearance Leads: New Device Decisions](https://apify.com/infocomp/fda-510k-clearance-leads): companies that just got a medical device cleared by FDA: new 510(k) decisions from openFDA.

### Limits

- HUD's coverage date is 12/2025. Management companies, phones and contracts may have changed since then.
- Only the property's **main** contract is shown (`CONTRACT1`). Use `contract_count` to spot properties with more than one contract.
- Some properties have no REAC score, contract or phone. Filters that need those fields skip such properties at no charge.

# Actor input Schema

## `states` (type: `array`):

Two-letter codes or US state names of the property, e.g. TX, Florida. Empty = all states and territories (about 23,800 properties).

## `cities` (type: `array`):

Optional. Property city names, e.g. Houston, San Antonio. Matches the start of the city name.

## `minUnits` (type: `integer`):

Optional. Only properties with at least this many apartment units.

## `contractExpiringWithinMonths` (type: `integer`):

Optional. Only properties whose main HUD assistance contract expires within this many months from today. Example: 24.

## `maxReacScore` (type: `integer`):

Optional. Only properties whose last REAC physical inspection scored at or below this (e.g. 70). Properties with no score are skipped.

## `onlyTroubledOrWatchList` (type: `boolean`):

Only properties HUD marks as troubled or potentially troubled, or that are on HUD's watch list.

## `managementCompany` (type: `string`):

Optional. Only properties whose management company name contains this text, e.g. 'National Church Residences'.

## `onlyWithCompanyPhone` (type: `boolean`):

Skip properties whose management company has no phone shared by 2+ of its staff in HUD's data (see README). Skipped rows are free.

## `maxResults` (type: `integer`):

Stop after this many property leads. Each lead is one charged row. Texas has about 1,000 properties; the US about 23,800.

## Actor input object example

```json
{
  "states": [
    "TX"
  ],
  "cities": [],
  "onlyTroubledOrWatchList": false,
  "onlyWithCompanyPhone": false,
  "maxResults": 25
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (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 = {
    "states": [
        "TX"
    ],
    "cities": [],
    "maxResults": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("infocomp/hud-multifamily-leads").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 = {
    "states": ["TX"],
    "cities": [],
    "maxResults": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("infocomp/hud-multifamily-leads").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 '{
  "states": [
    "TX"
  ],
  "cities": [],
  "maxResults": 25
}' |
apify call infocomp/hud-multifamily-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,infocomp/hud-multifamily-leads"
        }
    }
}
```

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/n6DFBmQ9YlZayGMer/builds/1BhtzCKyVzhFZmU6V/openapi.json