# Disaster Declaration Tracker — FEMA Declarations by State (`m_ctim/disaster-declaration-tracker`) Actor Track new FEMA disaster declarations — fires, floods, hurricanes, severe storms — by state or incident type, the moment they're declared. For insurance claims teams, disaster recovery contractors, and emergency management watching for new activations. - **URL**: https://apify.com/m\_ctim/disaster-declaration-tracker.md - **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community) - **Categories:** News - **Stats:** 2 total users, 1 monthly users, 100.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/platform/actors/running/actors-in-store#pay-per-usage ## 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 ## Disaster Declaration Tracker — FEMA Declarations by State Track new FEMA disaster declarations — fires, floods, hurricanes, severe storms, and more — by state or incident type, the moment they're declared. Get the disaster number, declared programs, affected area, and a link to the FEMA disaster page. Built for insurance claims teams, disaster recovery contractors, and emergency management professionals watching for new activations, without checking FEMA's site by hand. ### Input ```json { "states": ["CA", "TX"], "incidentTypes": ["Fire", "Flood"], "daysBack": 30, "maxResults": 50 } ``` | Field | Type | Description | |---|---|---| | `states` | array of strings (optional) | Two-letter state codes to filter. Leave empty for nationwide. | | `incidentTypes` | array of strings (optional) | Only include these incident types (e.g. `"Fire"`, `"Flood"`, `"Hurricane"`, `"Severe Storm(s)"`). Leave empty for all types. | | `daysBack` | number | How many days back from today to include, by declaration date. Default `30`, max `365`. | | `maxResults` | number | Max declarations to return, most recently declared first. Default `50`, max `200`. | ### Output One record per declaration: ```json { "femaDeclarationString": "FM-5668-NV", "disasterNumber": 5668, "state": "NV", "declarationType": "FM", "declarationTitle": "STALLION FIRE", "incidentType": "Fire", "declarationDate": "2026-08-11T00:00:00.000Z", "incidentBeginDate": "2026-08-10T00:00:00.000Z", "incidentEndDate": null, "designatedArea": "Washoe (County)", "iaProgramDeclared": false, "paProgramDeclared": true, "ihProgramDeclared": false, "hmProgramDeclared": false, "region": 9, "url": "https://www.fema.gov/disaster/5668" } ``` ### How it works Direct calls to the official [OpenFEMA API](https://www.fema.gov/about/openfema/api) (`DisasterDeclarationsSummaries` dataset). No proxy, no key, no scraping. ### Pricing note Billed per **search**, not per declaration returned — one charge whether the search returns 1 declaration or 200. ### Related products - [Field Operations Risk Briefing](https://github.com/timmKal01/field-operations-risk-briefing) — current weather/GPS/radio conditions at a location, rather than declared disasters - [Earthquake Alert](https://github.com/timmKal01/earthquake-alert) — a different hazard type (seismic activity) not covered by FEMA declarations # Actor input Schema ## `states` (type: `array`): Two-letter state codes to filter (e.g. "CA", "TX"). Leave empty for nationwide. ## `incidentTypes` (type: `array`): Only include these incident types (e.g. "Fire", "Flood", "Hurricane", "Severe Storm(s)"). Leave empty for all types. ## `daysBack` (type: `integer`): How many days back from today to include, by declaration date. ## `maxResults` (type: `integer`): Maximum number of declarations to return, most recently declared first. ## Actor input object example ```json { "daysBack": 30, "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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("m_ctim/disaster-declaration-tracker").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("m_ctim/disaster-declaration-tracker").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/disaster-declaration-tracker --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/disaster-declaration-tracker" } } } ``` 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 ` 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/n70mOfnYpaVNB36GK/builds/NaA6hjetFYoNwOPOu/openapi.json