# FEMA NFIP Flood Claims Search — Fast OpenFEMA API (`quartz_apple_dnx/fema-nfip-flood-claims-search-api`) Actor

Search FEMA's public privacy-redacted NFIP flood-claims dataset by state, county FIPS, ZIP, loss year and flood zone. Area-level analysis only; independent tool, not affiliated with or endorsed by FEMA.

- **URL**: https://apify.com/quartz_apple_dnx/fema-nfip-flood-claims-search-api.md
- **Developed by:** [Piven Core](https://apify.com/quartz_apple_dnx) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.25 / 1,000 nfip claims

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

## FEMA NFIP Flood Claims Search — Fast OpenFEMA API

Search FEMA's public, privacy-redacted National Flood Insurance Program claims data for **area-level flood-loss research and analysis**.

Use it for regional loss research, historical NFIP analysis, disaster-data workflows, public-data studies, and structured flood-claims datasets—without attempting to identify individual policyholders or properties.

**Independent tool. Not affiliated with or endorsed by FEMA. Not insurance, legal, underwriting, or property-identification advice.**

### Common use cases

- Analyze privacy-redacted NFIP claims by state, county, ZIP, or loss year
- Study reported flood-loss and payment patterns at an area level
- Filter public claims by flood zone or paid-claim status
- Build structured NFIP datasets for research or reporting
- Feed public flood-claims records into downstream analysis workflows

### What you get

One row per privacy-redacted NFIP claim can include loss date/year, event, state/county/ZIP, NFIP community, rated/current flood zone, occupancy/building indicators, reported damage, building/contents/ICC payments, coverage amounts, source vintage, exact source URL, and retrieval timestamp.

### Source

Current source:

`https://www.fema.gov/api/open/v3/NfipClaims`

This Actor intentionally uses FEMA's current v3 `NfipClaims` dataset. The older v2 `FimaNfipClaims` endpoint is deprecated and scheduled for retirement in October 2026.

OpenFEMA is public and does not require registration or an API key.

### Input

Filter by:

- state;
- 5-digit county FIPS;
- reported ZIP;
- loss-year range;
- exact rated flood zone;
- paid claims only;
- maximum rows.

The Store default searches paid Florida claims from 2022 and saves at most 25 rows.

### Privacy and interpretation boundaries

The underlying dataset is already privacy-redacted by FEMA. This Actor adds stricter product boundaries:

- no names or policyholder identity;
- no street-address input;
- no address lookup;
- no latitude/longitude output;
- no reverse identification;
- no claim that a row belongs to a specific property or person.

Reported ZIP, county and community fields are for area-level analysis. FEMA's redacted location information can be imprecise.

This dataset covers NFIP claims only. It does not include private-market flood claims and should not be used to infer flood probability, insurance pricing, eligibility, or a specific property's claim history.

### Pricing

Only successfully saved claim rows are billed. Legitimate zero-result and budget-limit summary rows are not billed.

Private candidate target: **$0.25 per 1,000 claim rows** ($0.00025 each), only if the private benchmark clears the factory's 3× economics gate.

Public release is a separate decision.

### About Piven Core

Built and maintained by **Piven Core** — focused data APIs and automation utilities for reliable, production-ready workflows.

Learn more: https://pivencore.com

# Actor input Schema

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

Optional 2-letter state or territory code.

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

Optional 5-digit county FIPS code.

## `zipCode` (type: `string`):

Optional 5-digit reported ZIP code. Use for area-level analysis only.

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

Optional earliest NFIP loss year to include.

## `yearOfLossTo` (type: `integer`):

Optional latest NFIP loss year to include.

## `floodZone` (type: `string`):

Optional exact rated NFIP flood zone, such as AE or X.

## `paidOnly` (type: `boolean`):

Require a positive building or contents claim payment.

## `maxRows` (type: `integer`):

Hard cap on saved billable claim rows.

## Actor input object example

```json
{
  "state": "FL",
  "yearOfLossFrom": 2022,
  "yearOfLossTo": 2022,
  "paidOnly": true,
  "maxRows": 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 = {
    "state": "FL",
    "yearOfLossFrom": 2022,
    "yearOfLossTo": 2022,
    "paidOnly": true,
    "maxRows": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("quartz_apple_dnx/fema-nfip-flood-claims-search-api").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 = {
    "state": "FL",
    "yearOfLossFrom": 2022,
    "yearOfLossTo": 2022,
    "paidOnly": True,
    "maxRows": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("quartz_apple_dnx/fema-nfip-flood-claims-search-api").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 '{
  "state": "FL",
  "yearOfLossFrom": 2022,
  "yearOfLossTo": 2022,
  "paidOnly": true,
  "maxRows": 25
}' |
apify call quartz_apple_dnx/fema-nfip-flood-claims-search-api --silent --output-dataset

```

## MCP server setup

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

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/xH24SoucpyaGbs3zi/builds/udRWbeXqzYjbiH4OZ/openapi.json