# Flood Zone Property Owner Leads & FEMA Flood Map Lookup (`scrapebench/flood-zone-property-owner-leads`) Actor

Every property in a FEMA flood zone, or about to enter one on a new FEMA map, with the owner's name and mailing address, in 20 states. Or the flood zone, panel and LOMA of any US address.

- **URL**: https://apify.com/scrapebench/flood-zone-property-owner-leads.md
- **Developed by:** [ScrapeBench](https://apify.com/scrapebench) (community)
- **Categories:** Lead generation, Real estate
- **Security:** Limited permissions
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / flood-zone property with owner

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

## Flood Zone Property Owner Leads & FEMA Flood Map Lookup

### Pain points

- FEMA's flood map shows one address at a time; it has no list of the properties inside a zone, and no owners.
- The owner is on a different site: the county assessor's roll, which knows nothing about flood zones.
- New flood maps are published as GIS layers and PDFs, so finding the owners a new map pulls into the flood zone means overlaying two datasets yourself.
- A zone alone misleads: a Letter of Map Amendment can have taken the house out of the zone, and the community's CRS class changes what insurance costs.

### What we solve

- FEMA's effective, pending and preliminary flood maps joined to official assessor rolls: one row per property, owner and mailing address on the row.
- A 'map change' filter for properties entering (or leaving) the flood zone on an adopted map with an effective date, or on a preliminary map.
- Each row checked against FEMA's LOMA letters (dropped by default when the letter removed the structure), with the panel, base flood elevation, CRS class and SFHA discount.
- Absentee, owner-type, property-use, value and year-built filters from the roll; government land left out unless you ask for it.

### Summary

Pick a county, a state or a ZIP and get every property inside FEMA's Special Flood Hazard Area, with the owner's name and mailing address from the assessor roll, the flood zone, base flood elevation, FIRM panel, the NFIP community's CRS discount and a pre-FIRM flag. Or ask for the properties that a pending or preliminary FEMA map moves INTO the flood zone, before the new map takes effect. Lookup mode answers the same questions for any US address.

### Who it's for

- Flood insurance agents and agencies (NFIP and private flood) looking for owners who need a policy
- Elevation certificate surveyors, flood vent and mitigation contractors, home-elevation companies
- Real estate investors and wholesalers screening flood risk, or looking for absentee owners in flood zones
- Lenders, title companies, appraisers and home buyers checking a property's zone and pending map change
- Floodplain managers, planners and researchers counting what a new FEMA map changes

### How to use

This actor does two jobs. Run it, then collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API).

**Get a list (export):** no names, just filters; returns the whole matching list.

```json
{
  "areas": [
    "Pinellas, FL"
  ],
  "absentee": [
    "out_of_state"
  ],
  "maxResults": 100
}
```

**Check specific addresses (lookup):** put US street addresses (with a unit number for a condominium) in `mode`, `addresses`; **Inputs** below says how each is matched.

```json
{
  "mode": "lookup",
  "addresses": [
    "1001 Ocean Dr, Miami Beach, FL 33139",
    "814 N Fort Fisher Blvd, Kure Beach, NC 28449"
  ]
}
```

See **Inputs** below for every available field.

### What you get

One row per record:

| Field | Description |
|---|---|
| `address` | Property street address (the roll's situs address in an export, the geocoder's matched address in a lookup) |
| `city` | Property city as the roll or the geocoder writes it |
| `state` | Two-letter state |
| `zip` | Property ZIP code, where the roll publishes one |
| `county` | County name |
| `parcel_id` | The assessor's parcel number |
| `latitude` | The point the flood zone was read at (the parcel's centroid, or the geocoded address) |
| `longitude` | The point the flood zone was read at |
| `flood_zone` | FEMA flood zone on the effective map: A, AE, AH, AO, AR, A99, V, VE, X or D |
| `zone_subtype` | FEMA's subtype, e.g. '0.2 PCT ANNUAL CHANCE FLOOD HAZARD' or 'AREA WITH REDUCED FLOOD RISK DUE TO LEVEE' |
| `in_sfha` | Inside the Special Flood Hazard Area (the 1%-annual-chance zone where a federally backed mortgage requires flood insurance) |
| `base_flood_elevation_ft` | FEMA's base flood elevation for the zone, where the map gives one |
| `flood_depth_ft` | Flood depth for AO zones |
| `vertical_datum` | Datum of the base flood elevation (NAVD88, NGVD29) |
| `firm_panel` | The Flood Insurance Rate Map panel number |
| `panel_effective_date` | When that FIRM panel took effect |
| `map_change` | none, pending_in / pending_out (an adopted map with an effective date moves it into / out of the SFHA), preliminary_in / preliminary_out, or \*\_rezone (a different zone, same SFHA status) |
| `pending_zone` | The zone on the pending (adopted, not yet effective) FEMA map |
| `pending_effective_date` | When the pending map takes effect |
| `preliminary_zone` | The zone on FEMA's preliminary map |
| `preliminary_issue_date` | When FEMA issued the preliminary map |
| `loma_case` | FEMA Letter of Map Amendment / Revision case number at this property, if any |
| `loma_outcome` | FEMA's determination, e.g. 'Structure removed' |
| `loma_removed` | True when the letter removed the structure from the flood zone |
| `community_id` | The National Flood Insurance Program community number |
| `community_name` | The NFIP community's name |
| `nfip_participating` | Whether the community takes part in the NFIP (no NFIP policy can be written where it does not) |
| `crs_class` | The community's Community Rating System class (1 best, 10 none) |
| `crs_sfha_discount` | The NFIP premium discount the CRS class gives inside the SFHA |
| `initial_firm_date` | When the community's first Flood Insurance Rate Map took effect |
| `pre_firm` | Built on or before 1974 or before the community's initial FIRM (from the roll's year built) |
| `owner_name` | Owner of record on the assessor roll |
| `owner_type` | individual, company, trust or government (read from the name) |
| `mailing_address` | The owner's mailing street address on the roll |
| `mailing_city` | The owner's mailing city |
| `mailing_state` | The owner's mailing state |
| `mailing_zip` | The owner's mailing ZIP |
| `absentee_tier` | out_of_state, out_of_city, same_city_diff_address, owner_occupied or unknown, from the mailing vs property address |
| `property_class_desc` | The roll's land-use description |
| `year_built` | Year built on the roll, where published |
| `market_value` | Market (just) value on the roll |
| `assessed_value` | Assessed value on the roll |
| `roll_source` | Which assessor roll the owner came from |
| `source_url` | The FEMA National Flood Hazard Layer service the zone was read from |

Sample:

```json
{
  "owner_name": "ULTRA BLUE PROPERTIES LLC",
  "owner_type": "company",
  "mailing_address": "4061 SANDVIEW DR",
  "mailing_city": "MEDINA",
  "mailing_state": "OH",
  "mailing_zip": "44256",
  "absentee_tier": "out_of_state",
  "address": "1515 PINELLAS BAYWAY S # 20",
  "city": "TIERRA VERDE",
  "state": "FL",
  "zip": "33715",
  "county": "Pinellas",
  "parcel_id": "16 32 29 94825 002 0200",
  "flood_zone": "AE",
  "zone_subtype": "COASTAL FLOODPLAIN",
  "in_sfha": true,
  "base_flood_elevation_ft": 9.0,
  "vertical_datum": "NAVD88",
  "firm_panel": "12103C0286H",
  "panel_effective_date": "2021-08-24",
  "map_change": "none",
  "pending_zone": null,
  "pending_effective_date": null,
  "loma_case": null,
  "community_name": "PINELLAS COUNTY *",
  "crs_class": "2",
  "crs_sfha_discount": "40%",
  "initial_firm_date": "1971-06-18",
  "pre_firm": false,
  "property_class_desc": "Condominium",
  "year_built": 1990,
  "market_value": 323847,
  "latitude": 27.671588,
  "longitude": -82.724803
}
```

### Inputs

| Field | Required | Type | Default | Description |
|---|---|---|---|---|
| `mode` | no | string | `"export"` | Export: every property in a FEMA flood zone (or about to enter or leave one) in the areas you list, with the owner's name and mailing address. Lookup: the FEMA flood zone, panel, pending map change and LOMA of each US address you list, plus the owner where the county is covered. |
| `areas` | no | array | `["New Hanover, NC"]` | One per line: a state ('FL'), a county ('Pinellas, FL' or 'FL/Pinellas'), a city ('Kure Beach, NC') or a 5-digit ZIP ('33139'). Run with no areas to get the coverage list for free. |
| `area` | no | string | — | One area, for saved tasks and API calls that send a single value. Use Areas above for several. |
| `addresses` | no | array | `[]` | One US street address per line, with city and state (a ZIP helps): '1001 Ocean Dr, Miami Beach, FL 33139'. Works anywhere FEMA has a digital flood map; the owner columns are filled where the county's roll is covered. |
| `address` | no | string | — | One address, for saved tasks and API calls that send a single value. |
| `sfhaOnly` | no | boolean | `true` | On: only properties inside FEMA's Special Flood Hazard Area (the 1%-annual-chance zones A and V, where a federally backed mortgage requires flood insurance). Off: every property in the area with its zone, including X. Ignored when 'Map change' is set. |
| `zones` | no | array | `[]` | Only these zones on the effective map. One per line: A, AE, AH, AO, AR, A99, V, VE (coastal), X_SHADED (0.2% annual chance), X_LEVEE (reduced risk behind a levee), X (minimal hazard), D (undetermined). Empty: any. X, X_SHADED and X_LEVEE need 'Only properties in the flood zone' off. |
| `mapChange` | no | string | `"all"` | Properties whose zone changes on a new FEMA map. 'Entering' = outside the SFHA today and inside it on a pending (adopted, with an effective date) or preliminary map; once the pending map takes effect, a federally backed mortgage will require flood insurance. 'Leaving' = the reverse. Pending maps cover about 100 map areas and preliminary maps about 400 in 2026, so many counties have none. |
| `excludeLoma` | no | boolean | `true` | On: a property with a completed LOMA that removed its structure from the flood zone is left out (its owner does not need flood insurance under the mortgage rule). Off: kept, with the case number. |
| `preFirmOnly` | no | boolean | `false` | Only buildings built before the community's first flood map (or before 1975). Needs a roll that publishes year built. |
| `ownerTypes` | no | array | `[]` | One per line: individual, company, trust, government. Empty: individual, company and trust (government land is left out of a lead list unless you ask for it). |
| `absentee` | no | array | `[]` | Only these owner-occupancy tiers, from the mailing address on the roll. One per line: out_of_state, out_of_city, same_city_diff_address, owner_occupied, unknown. Empty: any. |
| `propertyUse` | no | array | `[]` | Words matched against the roll's land-use description or code, one per line: 'single family', 'condominium', 'commercial', 'vacant'. Each county words it differently. Empty: any. |
| `zipCodes` | no | array | `[]` | Only properties in these 5-digit ZIP codes (where the roll publishes the property ZIP). |
| `minValue` | no | integer | — | Market (or assessed) value on the roll. |
| `maxValue` | no | integer | — | Market (or assessed) value on the roll. |
| `builtAfter` | no | integer | — | Year built on the roll; properties with no year are left out when set. |
| `builtBefore` | no | integer | — | Year built on the roll; properties with no year are left out when set. |
| `maxResults` | no | integer | `100` | Cap on owner rows per area line (not per run). 0 = no cap. A whole coastal state can hold hundreds of thousands of flood-zone parcels; start with a county. |
| `listCoverage` | no | boolean | `false` | Return the states and counties the export covers, and nothing else. |
| `proxyConfiguration` | no | object | `{"useApifyProxy": false}` | Off by default: FEMA, the Census geocoder and the county rolls are public services. Turn it on only if a run reports a source as blocked. |

### Pricing (Pay Per Event)

You pay per result (`owner-row`) — **no charge for empty runs**. Example: **1000 flood-zone properties** at *$0.01/result* ≈ **$10.00**.

In lookup mode each address FEMA answers is charged once ($0.004, event "Address lookup"), owner columns included where the county is covered; an address the geocoder cannot find, or where FEMA has no digital map, is free. Compute is included; you pay only these events.

### Use cases

- Insurance prospecting: every owner-occupied or absentee property in a county's SFHA, with mailing addresses, for a direct-mail campaign.
- New-map outreach: owners whose property enters the flood zone on a pending FEMA map, with the date the map takes effect.
- Mitigation leads: pre-FIRM buildings in zone AE or VE, with year built and value.
- Investor screening: absentee owners of condominiums in coastal VE zones in one ZIP code.
- Due diligence: the zone, panel, pending change and LOMA of a list of addresses before a closing or a loan.

### Why this actor

- Owner name and mailing address on every export row, from the official assessor roll.
- Pending and preliminary FEMA map changes, not just today's zone.
- LOMA letters, CRS class and a pre-FIRM flag on the row.
- Lookup mode for any US address in the same columns.

### Limitations & updates

The export covers the states and counties in the FAQ, where the assessor roll publishes a point or shape for each parcel; elsewhere use lookup mode. The zone is read at the parcel's centroid and is not an official flood zone determination. Owners are the owner of record on the roll, which can lag a recent sale; some rolls do not publish year built or the property ZIP (New Hanover, NC has neither), so filters on those leave such counties' rows out. No phone numbers or emails.

### FAQ

**Which states and counties does the export cover?**

Every county in Arkansas, Connecticut, Florida, Massachusetts, Minnesota, Montana, New Jersey, New York, North Carolina and Wisconsin (New York and Minnesota publish a statewide roll for the counties that opt in; run with no areas to get the exact list for free), plus Maricopa AZ, Alameda and Sacramento CA, Denver CO, Fulton GA, Marion IN, Oakland and Wayne MI, Cuyahoga, Franklin and Hamilton OH, Philadelphia PA, Davidson TN and Salt Lake UT. Lookup mode works for any US address FEMA has a digital map for; it adds the owner where the county is in that list.

**Where do the flood zone and the owner come from?**

The zone, base flood elevation, panel, LOMA and map changes come from FEMA's National Flood Hazard Layer and its pending and preliminary map services; the CRS class and initial FIRM date from FEMA's NFIP Community Status Book (OpenFEMA). The owner, mailing address, value and year built come from the state or county assessor roll for the parcel. Each property is placed in its zone by the parcel's own centroid.

**What does 'entering the flood zone' mean?**

FEMA publishes new maps first as preliminary maps, then as pending maps once a community adopts them, with the date they take effect. 'Entering' returns properties outside the SFHA on today's map and inside it on the new one, with the pending map's effective date. On a pending map that date is when a federally backed mortgage starts to require flood insurance. In November 2026 FEMA's pending maps covered about 100 map areas and its preliminary maps about 400, so many counties have none; a county without one returns no rows for this filter.

**Do you return phone numbers or emails?**

No. No public flood map or assessor roll carries an owner's phone or email; the owner's name and mailing address are what is published.

**How accurate is the zone for a property?**

It is FEMA's zone at the parcel's centroid (or, in lookup mode, at the point the Census geocoder gives the address). A large or oddly shaped parcel can lie in more than one zone, and the zone at its centre may not be the one under the building. It is not an official flood zone determination; a lender's determination or an elevation certificate is.

**What happens with condominiums?**

In an export every unit on the roll is its own row with its own owner. In lookup mode, an address that is a building with several units returns the owner only when the address includes the unit number ('1695 Pinellas Bayway S Unit A-5'); without one the flood columns are filled and the owner is left empty rather than guessed.

**How big is a run, and how long does it take?**

Measured on 2026-11-03: 1,000 flood-zone owner rows from New Hanover County, NC in 39 seconds, and 100 out-of-state owners in Pinellas County, FL in 66 seconds. A whole county's flood zone can be tens of thousands of properties, so set 'Maximum rows per area' to what you want to pay for, or narrow with ZIP codes. A county whose whole map is changing (Miami-Dade's pending map takes effect 2027-02-19) has much more FEMA map data to read and can take most of an hour.

**How am I charged?**

$0.01 per exported property row with an owner, and $0.004 per address answered in lookup mode. Coverage, no-match, no-digital-map and error rows are free.

### Which actor to choose

Works with:

- **US County Property Records Export** — You want every property in a county with values and sale history, flood zone or not.
- **Zillow & Redfin Property Scraper** — You want listing details, estimates and photos for specific addresses.

### Guides & use cases

Written up on **[scrapebench.dev](https://scrapebench.dev)** — the bench that runs and verifies this actor against the live source every night:

- **How-to:** [How to run Flood Zone Property Owner Leads & FEMA Flood Map Lookup](https://scrapebench.dev/guides/how-to-flood-zone-property-owner-leads/)
- **Use case:** [Pinellas County, FL flood zone property owners](https://scrapebench.dev/use-cases/pinellas-flood-zone-property-owners/)

More actors, coverage and nightly verification results: **[scrapebench.dev](https://scrapebench.dev)**

### Works with AI assistants (MCP)

Callable as an MCP tool, so Claude, Cursor, VS Code Copilot and other MCP clients can run it directly. Grab the config from the [MCP tab](https://apify.com/scrapebench/flood-zone-property-owner-leads/api/mcp) on this page — Apify hosts the server and keeps that snippet current, and OAuth signs you in on first connect, so no API token goes in your config file.

Then just ask:

> "List the out-of-state owners of properties in FEMA's flood zone in Pinellas County, Florida, with each owner's mailing address and the property's flood zone."

Ask for 'entering the flood zone' instead to get properties a pending FEMA map moves into the SFHA, or give a few street addresses to check their zones. Runs started this way bill exactly like any other run.

### Data & lawful use

This actor collects publicly available information that the Federal Emergency Management Agency (FEMA), the U.S. Census Bureau and the state and county assessors whose property rolls are listed in the coverage table publishes for public
lookup — licence records, business listings and the contact details professionals list there.
Some of it identifies individuals (sole proprietors, licence holders, agents), so treat any
names, phone numbers and emails in your results as personal data.

When you run this actor, you decide what is collected and what it is used for, so you are the
controller of that data and we act only as your processor (Apify Standard Actor Contract).
You need a lawful basis for your use, must honour opt-out and deletion requests, and must
follow the marketing rules that apply to you (CAN-SPAM, TCPA, GDPR, CCPA and similar).
Don't use the output for unsolicited bulk messaging, for screening covered by the FCRA, or
for anything the source's own terms forbid.

Your results are stored in your own Apify account. We don't keep a copy of your results and
don't sell or share them.

### Disclaimer

This is an independent tool. It is not affiliated with, endorsed by or sponsored by
the Federal Emergency Management Agency (FEMA), the U.S. Census Bureau and the state and county assessors whose property rolls are listed in the coverage table. Names and marks are used only to describe the data source. Records are
provided as published by the source and may be out of date or incomplete. For anything
consequential (hiring, a permit, a legal decision), confirm the record with the issuing
agency. You are responsible for making sure your use complies with applicable law and the
source's terms.

### Need help?

Open an issue on this actor's **Issues** tab and we'll respond there. Bug reports, missing
fields and feature requests are all welcome. Guides and examples: [scrapebench.dev](https://scrapebench.dev).

If you are a person named in this data and want your record removed from our copy, email
apify-help@scrapebench.dev; the source agency remains the official record.

Your run may be used to improve our services. If something looks off, or you want this actor to fit your use better, please share your run data with us: [Apify Console → Settings → Security → Share run data with developers](https://console.apify.com/settings/security). It lets us see exactly what went wrong and keep improving the actor.

# Actor input Schema

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

Export: every property in a FEMA flood zone (or about to enter or leave one) in the areas you list, with the owner's name and mailing address. Lookup: the FEMA flood zone, panel, pending map change and LOMA of each US address you list, plus the owner where the county is covered.

## `areas` (type: `array`):

One per line: a state ('FL'), a county ('Pinellas, FL' or 'FL/Pinellas'), a city ('Kure Beach, NC') or a 5-digit ZIP ('33139'). Run with no areas to get the coverage list for free.

## `area` (type: `string`):

One area, for saved tasks and API calls that send a single value. Use Areas above for several.

## `addresses` (type: `array`):

One US street address per line, with city and state (a ZIP helps): '1001 Ocean Dr, Miami Beach, FL 33139'. Works anywhere FEMA has a digital flood map; the owner columns are filled where the county's roll is covered.

## `address` (type: `string`):

One address, for saved tasks and API calls that send a single value.

## `sfhaOnly` (type: `boolean`):

On: only properties inside FEMA's Special Flood Hazard Area (the 1%-annual-chance zones A and V, where a federally backed mortgage requires flood insurance). Off: every property in the area with its zone, including X. Ignored when 'Map change' is set.

## `zones` (type: `array`):

Only these zones on the effective map. One per line: A, AE, AH, AO, AR, A99, V, VE (coastal), X_SHADED (0.2% annual chance), X_LEVEE (reduced risk behind a levee), X (minimal hazard), D (undetermined). Empty: any. X, X_SHADED and X_LEVEE need 'Only properties in the flood zone' off.

## `mapChange` (type: `string`):

Properties whose zone changes on a new FEMA map. 'Entering' = outside the SFHA today and inside it on a pending (adopted, with an effective date) or preliminary map; once the pending map takes effect, a federally backed mortgage will require flood insurance. 'Leaving' = the reverse. Pending maps cover about 100 map areas and preliminary maps about 400 in 2026, so many counties have none.

## `excludeLoma` (type: `boolean`):

On: a property with a completed LOMA that removed its structure from the flood zone is left out (its owner does not need flood insurance under the mortgage rule). Off: kept, with the case number.

## `preFirmOnly` (type: `boolean`):

Only buildings built before the community's first flood map (or before 1975). Needs a roll that publishes year built.

## `ownerTypes` (type: `array`):

One per line: individual, company, trust, government. Empty: individual, company and trust (government land is left out of a lead list unless you ask for it).

## `absentee` (type: `array`):

Only these owner-occupancy tiers, from the mailing address on the roll. One per line: out_of_state, out_of_city, same_city_diff_address, owner_occupied, unknown. Empty: any.

## `propertyUse` (type: `array`):

Words matched against the roll's land-use description or code, one per line: 'single family', 'condominium', 'commercial', 'vacant'. Each county words it differently. Empty: any.

## `zipCodes` (type: `array`):

Only properties in these 5-digit ZIP codes (where the roll publishes the property ZIP).

## `minValue` (type: `integer`):

Market (or assessed) value on the roll.

## `maxValue` (type: `integer`):

Market (or assessed) value on the roll.

## `builtAfter` (type: `integer`):

Year built on the roll; properties with no year are left out when set.

## `builtBefore` (type: `integer`):

Year built on the roll; properties with no year are left out when set.

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

Cap on owner rows per area line (not per run). 0 = no cap. A whole coastal state can hold hundreds of thousands of flood-zone parcels; start with a county.

## `listCoverage` (type: `boolean`):

Return the states and counties the export covers, and nothing else.

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

Off by default: FEMA, the Census geocoder and the county rolls are public services. Turn it on only if a run reports a source as blocked.

## Actor input object example

```json
{
  "mode": "export",
  "areas": [
    "New Hanover, NC"
  ],
  "addresses": [],
  "sfhaOnly": true,
  "zones": [],
  "mapChange": "all",
  "excludeLoma": true,
  "preFirmOnly": false,
  "ownerTypes": [],
  "absentee": [],
  "propertyUse": [],
  "zipCodes": [],
  "maxResults": 100,
  "listCoverage": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One row per property or address; free notice rows explain anything skipped.

# 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 = {
    "areas": [
        "New Hanover, NC"
    ],
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapebench/flood-zone-property-owner-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 = {
    "areas": ["New Hanover, NC"],
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapebench/flood-zone-property-owner-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 '{
  "areas": [
    "New Hanover, NC"
  ],
  "maxResults": 100
}' |
apify call scrapebench/flood-zone-property-owner-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapebench/flood-zone-property-owner-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/HGTs5xou4vOED8cgb/builds/zmxrdYqfpOY9sgwrC/openapi.json