# Flood Insurance Claims Data: FEMA NFIP Lookup (`m_ctim/fema-flood-claims-lookup`) Actor

Search official NFIP flood insurance claim history by state or county: damage amounts, flood zone, cause of damage, and payout totals. For real estate and flood insurance underwriting research. No key, no proxy.

- **URL**: https://apify.com/m\_ctim/fema-flood-claims-lookup.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** News
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

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

## FEMA Flood Claims Lookup: NFIP Data by State or County

Search official National Flood Insurance Program claim history by state or
county. Get back location, flood event, flood zone, damage amounts, and
payout totals per claim, straight from FEMA's own claims database.

### Who this is for

- **Real estate professionals** researching a property's or neighborhood's flood claim history before a transaction.
- **Flood insurance underwriters and risk analysts** assessing claim patterns by area.
- **Insurance and disaster-risk researchers** studying flood loss trends by state or county over time.

### Input

| Field | Type | Description |
|---|---|---|
| `state` | string | Two-letter US state code, e.g. `"TX"`. Provide this and/or `countyCode`. |
| `countyCode` | string | 5-digit county FIPS code, e.g. `"48201"` for Harris County, TX. |
| `yearOfLossFrom` | integer | Only include claims with a loss year at or after this. Leave blank for all years. |
| `maxResults` | integer (default `50`) | Cap on claims returned, most recent loss first. |

```json
{
  "state": "TX",
  "yearOfLossFrom": 2020,
  "maxResults": 50
}
```

### Output

One record per claim:

```json
{
  "state": "TX",
  "countyCode": "48201",
  "nfipCommunityName": "HOUSTON, CITY OF",
  "reportedZipCode": "77036",
  "latitude": 29.7,
  "longitude": -95.5,
  "dateOfLoss": "2020-09-18T00:00:00.000Z",
  "yearOfLoss": 2020,
  "floodEvent": "Hurricane Laura",
  "ratedFloodZone": "A",
  "floodZoneCurrent": "A",
  "occupancyType": 1,
  "primaryResidenceIndicator": true,
  "buildingDamageAmount": 45000,
  "amountPaidOnBuildingClaim": 42000,
  "contentsDamageAmount": 12000,
  "amountPaidOnContentsClaim": 11000,
  "totalBuildingInsuranceCoverage": 200000,
  "totalContentsInsuranceCoverage": 50000,
  "causeOfDamage": "4",
  "waterDepth": 2,
  "elevatedBuildingIndicator": false,
  "originalConstructionDate": "1985-01-01T00:00:00.000Z",
  "id": 5448672
}
```

This is FEMA's public redacted claims dataset: individual claims are
included, but personally identifying details (names, exact addresses) are
removed. `reportedZipCode`, `latitude`/`longitude`, and `nfipCommunityName`
place the claim at neighborhood level, not exact address.

### How it works

One direct call to the OpenFEMA NFIP Redacted Claims v3 API
(`fema.gov/api/open/v3/NfipClaims`), no scraping, no key, no proxy. Uses
the newer v3 endpoint since FEMA has deprecated v2 and stopped updating it.

### Related products

- [FEMA Disaster Assistance Tracker](https://github.com/timmKal01/fema-disaster-assistance-tracker): individual disaster assistance registrant activity, a broader signal than flood-specific claims
- [Disaster Declaration Tracker](https://github.com/timmKal01/disaster-declaration-tracker): new FEMA disaster declarations, upstream of the claims this actor searches
- [Coastal Water Level Tracker](https://github.com/timmKal01/coastal-water-level-tracker): real-time NOAA tide data, for current coastal flood risk rather than historical claims

# Actor input Schema

## `state` (type: `string`):

Two-letter US state code, e.g. "TX". Provide this and/or countyCode.

## `countyCode` (type: `string`):

5-digit county FIPS code, e.g. "48201" for Harris County, TX. Provide this and/or state.

## `yearOfLossFrom` (type: `integer`):

Only include claims with a loss year at or after this year. Leave blank for all years.

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

Maximum number of claims to return, most recent loss first.

## Actor input object example

```json
{
  "maxResults": 50
}
```

# Actor output Schema

## `results` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("m_ctim/fema-flood-claims-lookup").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("m_ctim/fema-flood-claims-lookup").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 '{}' |
apify call m_ctim/fema-flood-claims-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/fema-flood-claims-lookup"
        }
    }
}
```

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/HTuAnmPTk6tTVC3gO/builds/paEyUmpXPVzCOuTHR/openapi.json