OpenFEMA NFIP Flood Insurance Claims API

OpenFEMA NFIP flood-insurance claim public records — losses, zones and amounts paid.

Factual public records — assembled for research and monitoring.

📊 Sample Output

state	countyCode	dateOfLoss	yearOfLoss	ratedFloodZone	originalConstructionDate
TX	48135	2026-05-27T00:00:00.000Z	2026	AE	1950-01-01T00:00:00.000Z
TX	48061	2026-05-27T00:00:00.000Z	2026	X	1962-01-01T00:00:00.000Z
TX	48355	2026-05-27T00:00:00.000Z	2026	C	1999-01-01T00:00:00.000Z
TX	48409	2026-05-27T00:00:00.000Z	2026	X	1977-01-05T00:00:00.000Z
TX	48355	2026-05-27T00:00:00.000Z	2026	C	1983-01-01T00:00:00.000Z
TX	48397	2026-05-27T00:00:00.000Z	2026	X	1985-04-01T00:00:00.000Z

Real rows from run 7FwynCwlwJh6xBGN3 on build 0.0.16 (2026-09-24), unedited apart from masked emails/phones and shortened long text; fields the source does not publish are empty.

⚙️ Sample inputs

This is the Store example input — the same input Apify's automated check runs — so it is proven to return rows on the current build. Paste it into the input form, or send it through the API, CLI or a schedule:

{
  "state": "TX"
}

🔧 Input reference

Field	Type	Default	What it does
state	string	"TX"	Two-letter state code (e.g. TX, FL, LA).
yearOfLossFrom	integer		Only claims with year of loss >= this.
maxResults	integer	1000	Maximum claims to return.

🧾 JSON sample record

One real record from run 7FwynCwlwJh6xBGN3 (emails/phones masked, long text shortened):

{
  "state": "TX",
  "countyCode": "48135",
  "dateOfLoss": "2026-05-27T00:00:00.000Z",
  "yearOfLoss": 2026,
  "ratedFloodZone": "AE",
  "occupancyType": 11,
  "amountPaidOnBuildingClaim": null,
  "amountPaidOnContentsClaim": null,
  "totalBuildingInsuranceCoverage": 136000,
  "totalContentsInsuranceCoverage": 20000,
  "floodEvent": null,
  "latitude": 31.9,
  "longitude": -102.4,
  "originalConstructionDate": "1950-01-01T00:00:00.000Z"
}

💰 Pricing

Event	Price (USD)	When it is charged
Actor Start (apify-actor-start)	$0.01	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Mention (apify-default-dataset-item)	$0.05	Single brand mention with sentiment analysis.

Pay-per-event: you pay only for what the run delivers. A run that delivers nothing bills no result events (only the actor-start event, when the actor defines one). Example: a run that delivers 100 results costs 100 × $0.05 = $5.00 plus the start fee.

🔗 Related Actors

More from the NexGenData Data APIs family:

• Kuaishou Trending Tracker — 快手热榜 Hot Board API
• Landing Page Change Monitor — Track Competitor Pages
• NBA Scores — Live Stats & Game Data
• RECAP PACER Federal Docket Search API
• Regulatory Enforcement to Markdown — RAG Data API
• SERP Rank Tracker Lite

27 more in this family on the NexGenData Store page.

📊 What you get

Clean JSON, one record per claim (full output has 14 fields):

• state — State
• countyCode — County Code
• dateOfLoss — Date Of Loss
• yearOfLoss — Year Of Loss
• ratedFloodZone — Rated Flood Zone
• occupancyType — Occupancy Type
• amountPaidOnBuildingClaim — Amount Paid On Building Claim
• amountPaidOnContentsClaim — Amount Paid On Contents Claim
• totalBuildingInsuranceCoverage — Total Building Insurance Coverage
• totalContentsInsuranceCoverage — Total Contents Insurance Coverage

Pricing: $0.05 per claim (Pay-Per-Event) — about 20 per $1. Actor start fee $0.01 per run. Live prices are in the Pricing table below.

🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or any MCP-aware client at it and pull official records on demand.

Agentic payments (x402): Supports agentic payment via x402 — agents can call this actor with USDC, no API key required.

🔗 Related regulatory actors

Regulatory & enforcement records:

US Legislation · UK FCA Notices · UK FCA Register · EPA ECHO · EPA TRI · CFPB Complaints · CFPB HMDA

Related: SAM.gov Exclusions

---

Public official records and enforcement data, assembled for research and monitoring.