FEMA Disaster Declarations Scraper

🌪️ FEMA disaster declarations scraper for OpenFEMA records

FEMA Disaster Declarations Scraper collects official OpenFEMA disaster declaration area records from historical records back to 1953 through current records when available. It is built for researchers, emergency management teams, public-sector analysts, journalists, and developers who need structured declaration records without writing OData queries or using a FEMA API key.

Each result is one disaster declaration area record with FEMA identifiers, dates, incident type, state, designated area, assistance program flags, geography codes, source refresh metadata, and an official source URL when available.

• Build a FEMA disaster declarations dataset for a state, territory, tribal area, or national historical export.
• Track recent disaster declarations by incident type, declaration type, date range, or fiscal year.
• Audit which counties or designated areas received Individual Assistance, Public Assistance, Hazard Mitigation, or related program declarations.
• Join FEMA declaration numbers, FIPS-style codes, place codes, and designated areas into emergency management or public policy workflows.
• Export OpenFEMA disaster declaration records to spreadsheets, dashboards, databases, or downstream Apify automations.

📦 What data you get

The actor returns one row per accepted FEMA disaster declaration area record. Common fields include:

Field	Description
id	Stable OpenFEMA disaster declaration area record identifier.
disasterNumber	FEMA disaster declaration number.
state	Official FEMA state, territory, or tribal area code.
designatedArea	County, parish, municipality, tribal area, or other covered area.
declarationTitle	Official FEMA declaration title.
incidentType	Official FEMA incident type.
declarationType	FEMA declaration type code, such as DR, EM, or FM.
declarationDate	Date when the declaration was issued.
fiscalYear	FEMA fiscal year for the declaration.
incidentBeginDate / incidentEndDate	Official incident dates when provided.
ihProgramDeclared, iaProgramDeclared, paProgramDeclared, hmProgramDeclared	FEMA assistance program availability flags when available.
tribalRequest	Whether the declaration was requested by a tribal government when available.
fipsStateCode, fipsCountyCode, placeCode	Official geographic codes supplied by FEMA when available.
lastRefresh	OpenFEMA source refresh timestamp when available.
sourceUrl	Official OpenFEMA source URL for auditability.

▶️ How to run

1. Open the actor on Apify.
2. Set optional filters such as states, incident types, declaration types, declaration dates, fiscal years, or maximum results.
3. Start the run.
4. Download results from the dataset as JSON, CSV, Excel, XML, RSS, or HTML, or send them to another workflow.

You can run a broad export with no filters, or narrow the search to a state, incident type, declaration type, date range, year range, fiscal year, and maximum result count.

🎛️ Input options

Input	Use it to
states	Filter by state, territory, or tribal area. Common state names and two-letter codes are supported where practical.
incidentTypes	Filter by official FEMA incident type, such as Hurricane, Flood, Fire, or Severe Storm.
declarationTypes	Filter by FEMA declaration type code, such as DR, EM, or FM.
declarationDateFrom / declarationDateTo	Limit results by declaration date range.
declarationYearFrom / declarationYearTo	Limit results by declaration year range.
fiscalYears	Filter by FEMA fiscal year.
maxResults	Stop after a chosen number of declaration records.

🧾 Output example

{
  "id": "DR-4702-TX-201",
  "disasterNumber": 4702,
  "declarationRequestNumber": "23020",
  "state": "TX",
  "designatedArea": "Harris (County)",
  "declarationTitle": "Severe Storms, Straight-line Winds, and Tornadoes",
  "incidentType": "Severe Storm",
  "declarationType": "DR",
  "declarationDate": "2023-04-21T00:00:00.000Z",
  "fiscalYear": 2023,
  "incidentBeginDate": "2023-03-31T00:00:00.000Z",
  "incidentEndDate": "2023-04-01T00:00:00.000Z",
  "disasterCloseoutDate": "2024-06-12T00:00:00.000Z",
  "region": 6,
  "ihProgramDeclared": true,
  "iaProgramDeclared": true,
  "paProgramDeclared": true,
  "hmProgramDeclared": true,
  "tribalRequest": false,
  "fipsStateCode": "48",
  "fipsCountyCode": "201",
  "placeCode": "990201",
  "lastRefresh": "2024-03-18T14:22:41.000Z",
  "sourceUrl": "https://www.fema.gov/openfema-data-page/disaster-declarations-summaries-v2"
}

💳 Pricing

This actor uses pay-per-event pricing. You are charged only when the actor saves an accepted disaster declaration to the dataset. Empty runs and setup checks should not be described as charged unless the pricing handoff says otherwise.

🔌 Integrations

Use this actor with Apify integrations, API clients, webhooks, scheduled runs, and dataset exports. Send results to spreadsheets, BI tools, databases, or your own app after each run.

❓ FAQ

Can I collect FEMA disaster declarations without a FEMA API key?

Yes. The actor uses the official OpenFEMA disaster declarations source and does not require you to provide FEMA credentials, an API key, or OData syntax.

What happens when my filters return no records?

The run completes successfully and does not emit misleading rows. You can adjust the filters and run it again.

Does this include every FEMA aid or recovery program?

No. This actor focuses on disaster declaration area records. It does not collect broader FEMA aid, housing assistance, NFIP flood insurance, underwriting, risk scores, or policy analysis.

Can I filter by county or designated area?

The current public inputs focus on state, incident type, declaration type, declaration dates, declaration years, fiscal years, and maximum results. County or designated area values are returned in the output when FEMA provides them.

Can I use it for historical disaster declaration research?

Yes. The product contract covers historical OpenFEMA disaster declaration records back to 1953 through current records when available from the source.

Is the data official FEMA data?

The output is collected from the official OpenFEMA disaster declarations data source and includes source traceability fields such as sourceUrl and lastRefresh when available.

📝 Changelog

• 0.0.1: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Other actors

• Disease Outbreak News Scraper ↗ - Collect public health outbreak notices for related emergency monitoring workflows.
• FEC Campaign Finance Scraper ↗ - Export official campaign finance records for public-sector research.
• Harris County Court Records Scraper ↗ - Gather county-level public court records for government data workflows.
• Hospital Price Transparency Scraper ↗ - Collect public hospital price transparency data for compliance analysis.
• EU Funding Tenders Scraper ↗ - Track public funding and tender records for procurement research. Made with ❤️ by Maxime Dupré