# FEMA Disaster Declarations Scraper (`martc03/fema-disasters`) Actor

Extracts FEMA disaster declarations from the OpenFEMA API. Search by state, disaster type, date range. Hurricanes, floods, fires, and all federal emergencies.

- **URL**: https://apify.com/martc03/fema-disasters.md
- **Developed by:** [CoDee](https://apify.com/martc03) (community)
- **Categories:** Other, Automation
- **Stats:** 5 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## FEMA Disaster Declarations Tracker

The complete **US federal disaster declarations database** from [FEMA](https://www.fema.gov/), covering **69,000+ records** of hurricanes, floods, fires, tornadoes, earthquakes, and more — dating back to 1953.

### What data does it extract?

For each disaster declaration, the Actor extracts:

| Field | Description |
|-------|-------------|
| **Declaration** | FEMA declaration string (e.g., `DR-4844-FL`) |
| **State** | US state code |
| **Incident type** | Hurricane, Fire, Flood, Tornado, etc. (19 types) |
| **Title** | Disaster name (e.g., "HURRICANE MILTON") |
| **Declaration date** | When FEMA declared the disaster |
| **County/Area** | Specific affected county or tribal area |
| **Declaration type** | DR (Major Disaster), EM (Emergency), FM (Fire Management) |
| **Incident dates** | Begin and end dates of the incident |
| **Programs** | Which FEMA programs were activated (IH, IA, PA, HM) |
| **FEMA Region** | Federal region number (1-10) |
| **FIPS codes** | State and county FIPS codes for geographic mapping |

### Output example

```json
{
  "femaDeclarationString": "DR-4844-FL",
  "disasterNumber": 4844,
  "state": "FL",
  "declarationType": "DR",
  "declarationDate": "2024-11-05T00:00:00.000Z",
  "yearDeclared": 2025,
  "incidentType": "Hurricane",
  "declarationTitle": "HURRICANE MILTON",
  "incidentBeginDate": "2024-10-05T00:00:00.000Z",
  "incidentEndDate": "2024-11-02T00:00:00.000Z",
  "disasterCloseoutDate": null,
  "county": "Hillsborough (County)",
  "fipsStateCode": "12",
  "fipsCountyCode": "057",
  "femaRegion": 4,
  "ihProgram": true,
  "iaProgram": false,
  "paProgram": true,
  "hmProgram": true,
  "tribalRequest": false,
  "scrapedAt": "2026-02-18T18:00:00.000Z",
  "sourceUrl": "https://www.fema.gov/api/open/v2/DisasterDeclarationsSummaries"
}
```

### Input options

| Parameter | Type | Description |
|-----------|------|-------------|
| `states` | string\[] | Filter by state codes (e.g., `["CA", "FL", "TX"]`). Leave empty for all. |
| `incidentTypes` | string\[] | Filter by disaster type (e.g., `["Hurricane", "Fire"]`). Leave empty for all. |
| `declarationTypes` | string\[] | Filter by declaration type: `DR` (Major Disaster), `EM` (Emergency), `FM` (Fire Management). |
| `yearFrom` | integer | Only disasters declared on or after this year. |
| `yearTo` | integer | Only disasters declared on or before this year. |
| `maxRecords` | integer | Maximum records to fetch. Default: 10,000. Full database: 69,000+. |

### Incident types available

Biological, Coastal Storm, Dam/Levee Break, Earthquake, Fire, Flood, Freezing, Hurricane, Mud/Landslide, Severe Ice Storm, Severe Storm, Snowstorm, Straight-Line Winds, Tornado, Tropical Storm, Typhoon, Volcanic Eruption, Winter Storm, Other.

### Use cases

- **Insurance companies** - Assess disaster risk by county for underwriting and claims analysis
- **Real estate firms** - Evaluate property risk based on historical disaster patterns in an area
- **Emergency management** - Analyze disaster response patterns and resource allocation trends
- **Climate researchers** - Study long-term trends in disaster frequency and severity since 1953
- **Data journalists** - Report on disaster patterns, federal response times, and regional impacts
- **Government contractors** - Identify areas with active disaster recovery programs for FEMA contract opportunities
- **Risk analysts** - Build disaster probability models using 70+ years of historical data

### Data freshness

FEMA updates this database daily. Schedule this Actor to run daily or weekly to track new disaster declarations as they happen.

### Cost

This Actor uses the FEMA OpenFEMA API. Typical cost: **less than $0.01 per run** for up to 10,000 records.

# Actor input Schema

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

Filter by US state codes (e.g., \["CA", "FL", "TX"]). Leave empty for all states.

## `incidentTypes` (type: `array`):

Filter by disaster type (e.g., \["Hurricane", "Fire", "Flood"]). Options: Biological, Coastal Storm, Dam/Levee Break, Earthquake, Fire, Flood, Freezing, Hurricane, Mud/Landslide, Severe Ice Storm, Severe Storm, Snowstorm, Straight-Line Winds, Tornado, Tropical Storm, Typhoon, Volcanic Eruption, Winter Storm, Other.

## `declarationTypes` (type: `array`):

Filter by declaration type. DR = Major Disaster, EM = Emergency, FM = Fire Management. Leave empty for all.

## `yearFrom` (type: `integer`):

Only include disasters declared on or after this year (e.g., 2020).

## `yearTo` (type: `integer`):

Only include disasters declared on or before this year (e.g., 2026).

## `maxRecords` (type: `integer`):

Maximum number of records to fetch. The full database has 69,000+ records. Default: 10,000.

## Actor input object example

```json
{
  "maxRecords": 10000
}
```

# Actor output Schema

## `overview` (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("martc03/fema-disasters").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("martc03/fema-disasters").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 martc03/fema-disasters --silent --output-dataset

```

## MCP server setup

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

```

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/nWP8WMj7NuzoWlZG3/builds/kS2FYlKRvuIzBVT0C/openapi.json