ParseForge
FEMA Disaster Declarations Scraper
parseforge/fema-disaster-scraper
Developer toolsAutomationOther
Scrapes FEMA disaster declarations from public feeds. Filter by state, incident type, or fiscal year and export each declaration as a flat row.
- Total users
- 2
- Monthly active
- 0
- Total runs
- 140
- Bookmarked
- 0
- Rating
- Not rated yet
- Last modified
- 12 days ago
Overview
FEMA Disaster Declarations Scraper
Scrape FEMA disaster declarations by state, incident type, or fiscal year, up to a million per run. Every declaration comes with its incident type, state, and declaration date. No login or API key. Export to CSV, JSON, Excel, or XML.
FEMA's official OpenFEMA API needs an API key and rate-limits you. This reads the public disaster declaration feeds directly, filtered by state, incident type, or fiscal year, and returns each match in one fixed schema.
| Who uses it | What they scrape FEMA for |
|---|---|
| Insurance underwriters | Which counties have active federal disaster declarations for risk scoring |
| Emergency managers | Which incident types are declared most often in their state this year |
| Climate risk analysts | Historical declaration frequency by incident type for a region |
| Grant writers | Which recent declarations make a community eligible for FEMA aid |
| Journalists | Which disasters were declared in a state after a major storm |
What it does
This Actor collects FEMA disaster declarations by state, incident type, or fiscal year, and returns each one as a flat row.
- 📊 Computed signals: declaration date, incident type, and state for every record.
- 🔍 Flexible filters: narrow by state code, incident type, or fiscal year before the run.
- 📦 Bulk export: collect up to 1,000,000 declarations per run and export to CSV, JSON, Excel, or XML.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with FEMA data
📈 Track declaration trends.
A climate risk analyst pulls all flood declarations for Texas since 2010 to chart frequency and support a reinsurance pricing model.
🗺️ Map active disasters.
An emergency manager filters by state and current fiscal year to see which counties have open declarations and need resource allocation.
📋 Build grant eligibility lists.
A grant writer collects recent fire declarations in California to identify communities that qualify for FEMA public assistance.
📰 Verify disaster claims.
A journalist checks whether a county was under a federal declaration during a specific storm to fact-check a local official's statement.
Why choose this scraper
| What you get | |
|---|---|
| No API key | Reads the public FEMA feeds directly, no registration or OAuth. |
| One fixed schema | Every declaration returns the same flat fields, ready for analysis. |
| Bulk collection | Set maxItems up to 1,000,000 and pull a full history in one run. |
| Filtered at the source | State, incident type, and fiscal year filters reduce noise before storage. |
How it compares
This Actor focuses on bulk, filtered declaration collection without an API key, while the competitors below add monitoring, date ranges, or aid data.
| Feature | ParseForge | FEMA Disaster Declaration Search Monitor | FEMA Disaster Declarations Scraper | FEMA Disaster Declarations Scraper - Aid & Housing API |
|---|---|---|---|---|
| Filter by state | Yes | Yes | Yes | Yes |
| Filter by incident type | Yes | Yes | Yes | Yes |
| Filter by fiscal year | Yes | Not listed | Not listed | Yes |
| Bulk collection up to 1,000,000 records | Yes | Not listed | Not listed | Not listed |
| No API key required | Yes | Not listed | Not listed | Not listed |
| Aid and housing data | Not listed | Not listed | Not listed | Yes |
Configure the run
Drive the Actor from state codes, incident types, and fiscal years, alone or together, and filters run as each declaration is read so only matches reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
{
"maxItems": 10
}
A larger pull:
{
"maxItems": 200
}
Pricing
Pay-per-result: $0.007 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.70 |
| 1,000 results | $7.00 |
| 10,000 results | $70.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the FEMA Disaster Declarations Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to FEMA through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/fema-disaster-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Your filters may be too narrow. Remove the fiscal year or incident type and try again. Also confirm the state code is a valid two-letter code.
Why did the run stop before maxItems?
The Actor stops when it has collected maxItems declarations or when the source has no more matching records. Lower maxItems if you only need a sample.
Why is my state filter not working?
Use the two-letter US state code in uppercase, like TX for Texas. Do not use full state names.
Why is the output missing some fields?
The Actor returns the fields available in the public FEMA feed. Some declarations may lack optional fields like incident type if FEMA did not publish them.
Can I get data for a specific county?
No. This Actor filters by state, incident type, and fiscal year only. For county-level data, use a FEMA aid or housing scraper.
FAQ
| Question | Answer |
|---|---|
| Do I need a FEMA API key? | No. This Actor reads the public FEMA disaster declaration feeds directly, so no registration or key is required. |
| What incident types can I filter by? | Fire, Flood, Hurricane, Tornado, Severe Storm, Earthquake, Winter Storm, Drought, Coastal Storm, Typhoon, and Snowstorm. |
| Can I filter by state? | Yes. Use the state input with a two-letter US state code like TX, CA, or FL. |
| Can I filter by fiscal year? | Yes. Set fiscalYear to a four-digit year like 2024 to get only declarations from that federal fiscal year. |
| How many declarations can I get in one run? | Up to 1,000,000. Set maxItems to the number you need, and the Actor stops when it reaches that count. |
| What format is the output? | Each declaration is a flat row with fields like state, incident type, and declaration date. You can export to CSV, JSON, Excel, or XML. |
| Does this include housing assistance data? | No. This Actor returns disaster declarations only. For aid and housing data, use a dedicated FEMA aid scraper. |
| Is the data real-time? | The Actor reads the current public feeds at run time, so you get the latest declarations available. |
| Can I run this on a schedule? | Yes. Use Apify's scheduler to run it daily or weekly and track new declarations automatically. |
| What if I get no results? | Check your filters. A state code, incident type, and fiscal year combination may have no matching declarations. Try removing one filter. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Federal Emergency Management Agency. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
Input
| Field | Type | What it does | Default |
|---|---|---|---|
| state | string | Filter by US state code (e.g. TX, CA, FL) | not set |
| incidentType | string (11 options) | Filter by incident type | not set |
| fiscalYear | integer | Filter by fiscal year of declaration (e.g. 2024) | not set |
| maxItems | integer | How many disasters to collect per run. | 10 |
Pricing
from $6.50 per 1,000 results
| Charged for | What it is | Price each |
|---|---|---|
| result | Single result in the default dataset. | $0.0065 to $0.007 |
Tiered: the lower figure is the price on a higher Apify plan. Billing and the free credit live on Apify.
API
One POST returns the dataset directly. Same shape for every scraper in the library, so swapping the slug is the only change.
curl -X POST "https://api.apify.com/v2/acts/parseforge~fema-disaster-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"helloWorld": 123
}' Examples
Input that runs as-is.
{
"helloWorld": 123
} Reviews
No reviews yet. Be the first.
Issues
We build and maintain this scraper, so a problem with it comes to us. Report it on the Apify listing and the thread stays attached to the scraper where the next person can find it: open an issue.
Broken and urgent, or you would rather not post in public? Write to parseforge@protonmail.com and it reaches the people who wrote it.
Related scrapers
Run FEMA Disaster Declarations Scraper on Apify All scrapers