HUD Multifamily & Affordable Housing Leads avatar

HUD Multifamily & Affordable Housing Leads

Pricing

$6.00 / 1,000 housing record / leads

Go to Apify Store
HUD Multifamily & Affordable Housing Leads

HUD Multifamily & Affordable Housing Leads

Scrape official HUD open data: assisted/Section 8, FHA-insured, LIHTC & public-housing properties with management contacts (name, phone, email), units, REAC scores, loan-maturity & contract-expiry timing signals and a lead score. Filter by state, type & units. B2B leads + monitoring.

Pricing

$6.00 / 1,000 housing record / leads

Rating

0.0

(0)

Developer

Scrape Sage

Scrape Sage

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

HUD Multifamily & Affordable Housing Leads — Owners, Managers, Contacts & Inspection Data

Extract the entire HUD multifamily & affordable-housing portfolio as clean, contact-rich B2B leads — assisted / Section 8, FHA-insured, LIHTC tax-credit, and public-housing-authority properties in one unified schema. Every row ships the fields most lists leave blank: the management company, named contact, title, direct phone and email, plus units, occupancy, REAC inspection scores, financing, loan-maturity & contract-expiration timing signals, troubled/watch-list status, and a lead score.

No login, no cookies, no browser, no API key — fast JSON extraction straight from official HUD open data.

Why this HUD scraper?

Public HUD data is scattered across four separate datasets and buried in 280-column ArcGIS layers full of geocoder noise. This actor merges them, de-duplicates, surfaces the contacts and the high-intent signals, and scores every record:

DataTypical listsThis actor
Management company + named contact + title
Contact direct phone & email✅ (98% on assisted)
Assisted / Section 8 + FHA-insured + LIHTC + PHA in one schema❌ single dataset✅ all four
Units, assisted units, occupancy %partial
REAC physical-inspection score + date
Loan-maturity date (refinance timing)
Section 8 contract expiration (renewal timing)
Troubled / watch-list / default flags
LIHTC allocation $, target population, financing sources
Public housing authority exec-director phone & email
Lead score (0–100) + lead signals
Rich source-field passthrough (every meaningful native field)

Use cases

  • Property-management & proptech sales — reach the management company and named on-site contact at every assisted and FHA-insured property. Score by units (totalUnits) and contact them directly (bestEmail, bestPhone).
  • Affordable-housing finance & LIHTC — find owners with mortgages maturing soon (loanMaturingWithinMonths) or Section 8 contracts expiring (contractExpiringWithinMonths) for refinance, recapitalization and acquisition outreach.
  • Capital improvement / energy retrofit / ESCO — target properties with low REAC scores (reacScoreBelow) or troubled/watch-list status — the highest capital-needs intent.
  • Multifamily insurance & risk — build prospect lists by property type (senior, assisted living, nursing home), size and state.
  • Government / housing-authority vendors — sell software, modernization, RAD conversion and services to Public Housing Authorities with exec-director contacts and funding amounts.
  • Market & portfolio intelligence — map subsidized & tax-credit inventory by metro, units, rents and resident demographics.

How to use

  1. Sign up for Apify — the free plan is enough to try this actor.
  2. Open the HUD Multifamily & Affordable Housing Leads actor, choose your datasets and a state (or city / ZIP), set any filters, and click Start.
  3. Watch results stream into the dataset table.
  4. Export as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the Apify API.

Input

{
"datasets": ["assisted", "insured", "pha"],
"states": ["TX", "FL"],
"propertyTypes": ["senior", "assistedLiving"],
"minUnits": 50,
"hasEmail": true,
"loanMaturingWithinMonths": 24,
"maxResults": 1000,
"sortBy": "leadScore"
}
  • datasets (default assisted, insured, pha) — which HUD sources to merge. assisted (Section 8/202/811/PRAC) and insured (FHA) carry the richest contacts; pha adds housing-authority exec contacts; lihtc adds the largest property universe (allocation/units/target population — note HUD withholds owner contacts on most LIHTC rows).
  • states / cities / counties / zipCodes / nameQuery — location & name filters (combine with AND).
  • propertyTypesfamily, senior, assistedLiving, nursingHome, boardAndCare, hospital, disabled, elderly, homeless.
  • minUnits / maxUnits — size filters.
  • hasEmail / hasPhone — keep only contactable records.
  • subsidizedOnly / troubledOnly — Section 8 / active-assistance, or troubled / watch-list / default.
  • loanMaturingWithinMonths — refinance-timing signal (FHA-insured).
  • contractExpiringWithinMonths — Section 8 renewal-timing signal.
  • reacScoreBelow — capital-needs signal (low physical-inspection score).
  • sortByleadScore (recommended), unitsHigh, recentInspection, loanMaturitySoon, source.
  • monitorMode / monitorKey — only emit new / changed records since the last run (see below).

Output

One record per property or housing authority:

{
"recordType": "property",
"dataset": "assisted",
"recordId": "800023743",
"name": "CHEYENNE HANDICAPPED",
"address1": "1215 CLEVELAND AVE",
"city": "Cheyenne",
"county": "Laramie",
"state": "WY",
"zip": "82001",
"latitude": 41.1365,
"longitude": -104.7564,
"metroArea": "Cheyenne, WY Metropolitan Statistical Area",
"propertyCategory": "202/811",
"propertyTypes": ["senior"],
"totalUnits": 12,
"assistedUnits": 12,
"occupancyPct": 87.04,
"managementCompany": "MAGIC CITY ENTERPRISES, INC.",
"contactName": "Nancy Gordy",
"contactTitle": "Property Manager",
"contactPhone": "3077712812",
"contactEmail": "ngordy@mcewyo.org",
"financingType": "202/811",
"originalLoanAmount": 396800,
"loanMaturityDate": "2027-12-01",
"subsidyPrograms": ["Section 8"],
"contracts": [{ "number": "WY99T856003", "programType": "202/8 NC", "units": 12, "expirationDate": null }],
"reacInspectionScore": 99,
"reacInspectionDate": "2025-04-22",
"troubledStatus": "N",
"isOnWatchList": false,
"residentProfile": { "avgRentPerMonth": 343, "medianIncome": 13441, "pctElderly": 63.64 },
"bestEmail": "ngordy@mcewyo.org",
"bestPhone": "3077712812",
"leadScore": 80,
"leadSignals": ["Has contact email", "Has direct phone", "Named contact", "Management company identified", "Loan maturing within 24 months — refinance window", "Senior / elderly housing"],
"mapUrl": "https://www.google.com/maps/search/?api=1&query=41.1365,-104.7564",
"sourceFields": { "...": "every meaningful native HUD field, cleaned" },
"scrapedAt": "2026-06-20T22:55:00.000Z"
}

Public-housing-authority rows (recordType: "housingAuthority") add execDirectorPhone, execDirectorEmail, programType, phasDesignation, section8Units and a funding object (operating / capital / ROSS / FSS grants). LIHTC rows add allocationAmount, creditType, yearPlacedInService, targetPopulation, financingSources, difficultDevelopmentArea and qualifiedCensusTract.

Monitoring mode — only new & changed leads

Turn on monitorMode and the actor remembers every record it has returned (in a named key-value store) and emits only records that are new or whose key fields changed (contacts, units, REAC score, troubled status, loan/contract dates) since the last run — each tagged with a monitorEvent of new or updated.

This is complementary to, not a replacement for, Apify Schedules: the Schedule decides when the actor runs, monitoring decides what counts as new. Use a distinct monitorKey per saved watch (e.g. one per state or property type) so different monitors keep separate memory.

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });
const run = await client.actor('scrapesage/hud-multifamily-scraper').call({
datasets: ['assisted', 'insured'],
states: ['TX'],
minUnits: 100,
hasEmail: true,
sortBy: 'leadScore',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} HUD multifamily leads`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

  • Make — multi-step automation scenarios.
  • Zapier — push new property leads straight into your CRM.
  • Slack — get notified when a monitored watch finds new properties.
  • Google Drive / Sheets — auto-export every run to a spreadsheet.
  • Airbyte — pipe results into your data warehouse.
  • GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. You can call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "find senior HUD properties in Texas with a contact email and a low inspection score" and let it run this scraper for you.

More US B2B & real-estate data from scrapesage

Build a complete property & owner intelligence stack:

Tips

  • Target a market: always set a states filter (and optionally cities) for the fastest, cheapest runs. Without one, the actor scans the full national dataset(s).
  • Best contacts: keep datasets on assisted + insured and turn on hasEmail for the cleanest ready-to-contact list.
  • Refinance pipeline: combine datasets: ["insured"] with loanMaturingWithinMonths: 36 and sortBy: "loanMaturitySoon".
  • Turnaround / capex: set troubledOnly: true or reacScoreBelow: 60.
  • LIHTC market data: select datasets: ["lihtc"] and sortBy: "unitsHigh" — note these rows carry property & allocation data, not direct owner contacts.

FAQ

Where does the data come from? Official U.S. Department of Housing and Urban Development (HUD) open data — the Multifamily Assisted, HUD-Insured Multifamily, LIHTC and Public Housing Authority datasets published on HUD's open-data portal. No API key or login required.

Which datasets have contact details? The Assisted and FHA-Insured multifamily datasets carry management-company contacts (name, title, phone, email) on ~63–98% of rows. Public Housing Authorities carry agency and executive-director phone & email. LIHTC carries property, allocation and target-population data, but HUD withholds owner contacts on most LIHTC rows.

Why are some fields null? Fields are null only when HUD doesn't publish them for that record (e.g. an FHA-insured property with no Section 8 contract, or a property HUD never assigned a REAC score). The scraper never skips data that exists — and the full sourceFields object preserves every meaningful native field.

Can I export to Google Sheets, CSV, or Excel? Yes — one click in the dataset view, or automatically on every run via the Google Drive integration.

How do I get only new or changed properties? Turn on monitorMode and run on a Schedule. Each run emits only new or updated records.

Is this legal? This actor collects publicly available government data only. You are responsible for using it in compliance with applicable laws (including CAN-SPAM / TCPA for outreach and any privacy rules that apply to personal contact data).

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.