OpenFEMA NFIP Flood Insurance Claims API avatar

OpenFEMA NFIP Flood Insurance Claims API

Deprecated

Pricing

from $50.00 / 1,000 nfip claim records

Go to Apify Store
OpenFEMA NFIP Flood Insurance Claims API

OpenFEMA NFIP Flood Insurance Claims API

Deprecated

NFIP flood-insurance claims (redacted) by state and year: flood zone, amounts paid on building/contents, coverage, loss date, location. For P&C insurers, reinsurers, flood-risk and climate analysts.

Pricing

from $50.00 / 1,000 nfip claim records

Rating

0.0

(0)

Developer

NexGenData

NexGenData

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

0

Monthly active users

2 days ago

Last modified

Share

🌊 OpenFEMA NFIP Flood Insurance Claims API

NFIP flood-insurance claims as clean JSON or CSV, straight from FEMA's current claims dataset. Pick a state (and optionally a first loss year) and get one row per redacted claim: date of loss, flood event, flood zone, county, ZIP, coverage, net building and contents payments, damage amounts and cause of damage β€” newest losses first.

It is built for property & casualty insurers, reinsurers, catastrophe modellers, mortgage and real-estate risk teams, and climate researchers who need claim-level flood loss history without downloading and filtering FEMA's multi-million-row file themselves.

You pay per claim delivered β€” $0.05 per claim plus a $0.01 start fee. A run that returns no claims costs only the start fee.

Oct 21, 2026: FEMA retired the old FimaNfipClaims (v2) endpoint. This actor now reads the replacement dataset, NfipClaims version 3. Your inputs and the original 14 output fields are unchanged; 13 new fields from v3 were added.

πŸ“Š Sample Output

Six real NFIP claims from Texas: claim id, date of loss, county, ZIP, flood event, flood zone, net payments and coverage

Six real rows from run CFbUkugPPKl0stW9k (FEMA NfipClaims v3, Texas, Oct 21, 2026). Amounts in US dollars.

claimIddateOfLosscountyZIPfloodEventzonenetBuildingPaymentnetContentsPaymentbuildingCoverage
59427232026-07-1748463788012026-07-Texas-FloodingA138,03934,000182,000
79507772026-07-2148283780142026-07-Texas-FloodingA35,00010,00035,000
56168312026-07-234820177096X31,0090152,000
59616102026-09-0248199776252026-09-Edouard-TSX00200,000
73751472026-08-284820177008AE00250,000
67168152026-08-034816777650VE00200,000

Notice that recent claims (September 2026, Tropical Storm Edouard) show 0 net payment: they are still open. Claims from July 2026 already carry the settled payments. Re-run monthly to pick up payment updates.

βœ… What you get

One row per NFIP claim, 27 fields:

  • claimId β€” FEMA's record id for the claim (id in NfipClaims v3). Use it to de-duplicate across runs.
  • state β€” Two-letter state code of the insured property.
  • countyCode β€” 5-digit county FIPS code.
  • reportedZipCode β€” ZIP code of the insured property.
  • reportedCity β€” City as FEMA publishes it. FEMA currently returns "Currently Unavailable" for most rows.
  • nfipCommunityName β€” NFIP participating community (city or county) the policy is rated in.
  • latitude / longitude β€” Location rounded by FEMA to one decimal place (about 7 miles) for privacy.
  • dateOfLoss β€” Date the flood loss happened (ISO 8601).
  • yearOfLoss β€” Year of the loss β€” the field the yearOfLossFrom filter uses.
  • floodEvent β€” FEMA's name for the flood event, e.g. 2026-09-Edouard-TS. Empty when the loss is not tied to a named event.
  • causeOfDamage β€” FEMA cause-of-damage code (string). Empty on some open claims.
  • ratedFloodZone β€” Flood zone the policy is rated in (AE, X, A, VE …).
  • occupancyType β€” FEMA occupancy code (e.g. 11 = single-family residence).
  • primaryResidenceIndicator β€” true when the building is the policyholder's primary residence.
  • originalConstructionDate β€” Date the building was originally built.
  • totalBuildingInsuranceCoverage / totalContentsInsuranceCoverage β€” Coverage limits on the policy, in US dollars.
  • netBuildingPaymentAmount / netContentsPaymentAmount β€” Net amounts paid on the building and contents parts of the claim. 0 while a claim is still open or when nothing was paid.
  • netIccPaymentAmount β€” Net Increased Cost of Compliance payment.
  • buildingDamageAmount / contentsDamageAmount β€” Damage amounts assessed by the adjuster. Often empty until the claim is adjusted.
  • amountPaidOnBuildingClaim / amountPaidOnContentsClaim β€” The older paid-amount fields. FEMA still fills them on settled claims only (6 of 25 rows in the sample); the net payment fields above are filled on every row.
  • waterDepth β€” Water depth in inches inside the building, when reported.
  • asOfDate β€” Date of FEMA's data refresh that the row came from.

βš™οΈ Sample inputs

1. The Store example β€” the 25 most recent Texas claims. Costs $0.01 + 25 Γ— $0.05 = $1.26.

{
"state": "TX",
"maxResults": 25
}

2. Florida claims since 2024 β€” up to 1,000 rows (the default when maxResults is left out). At most $0.01 + 1,000 Γ— $0.05 = $50.01.

{
"state": "FL",
"yearOfLossFrom": 2024
}

3. A small Louisiana check β€” 100 claims, $5.01.

{
"state": "LA",
"maxResults": 100
}

πŸ”§ Input reference

FieldTypeDefaultWhat it does
statestringβ€”Two-letter state code (TX, FL, LA …). Leave empty for all states.
yearOfLossFromintegerβ€”Only claims with year of loss on or after this year.
maxResultsinteger1000Maximum claims to return (1–10,000 per run).

🧾 JSON sample record

{
"state": "TX",
"countyCode": "48463",
"dateOfLoss": "2026-07-17T00:00:00.000Z",
"yearOfLoss": 2026,
"ratedFloodZone": "A",
"occupancyType": 11,
"amountPaidOnBuildingClaim": 138038.96,
"amountPaidOnContentsClaim": 34000,
"totalBuildingInsuranceCoverage": 182000,
"totalContentsInsuranceCoverage": 34000,
"floodEvent": "2026-07-Texas-Flooding",
"latitude": 29.2,
"longitude": -99.8,
"originalConstructionDate": "1978-01-01T00:00:00.000Z",
"claimId": 5942723,
"asOfDate": "2026-09-08T00:00:00.000Z",
"reportedCity": "Currently Unavailable",
"reportedZipCode": "78801",
"nfipCommunityName": "UVALDE COUNTY*",
"causeOfDamage": "2",
"buildingDamageAmount": 136429,
"contentsDamageAmount": 37313,
"netBuildingPaymentAmount": 138038.96,
"netContentsPaymentAmount": 34000,
"netIccPaymentAmount": 0,
"waterDepth": 4,
"primaryResidenceIndicator": true
}

πŸ”§ How it works

  1. The actor queries FEMA's public OpenFEMA API at https://www.fema.gov/api/open/v3/NfipClaims, filtered by state and year of loss, ordered by date of loss (newest first), 1,000 rows per page.
  2. Each claim is mapped to the 27 fields above and pushed to the dataset; each pushed claim is charged once.
  3. If FEMA does not answer after 4 tries, the run fails with "FEMA data source unavailable after 4 tries β€” nothing charged per record." If FEMA answers but nothing matches your filters, the run succeeds with 0 rows and says so.

No login or API key is needed. FEMA redacts personal information before publishing; the actor does not add any.

πŸ’° Pricing

EventPrice (USD)When it is charged
Actor Start (apify-actor-start)$0.01Once when the run starts (one event per GB of memory; default memory is 256 MB, so one event).
NFIP claim record (apify-default-dataset-item)$0.05Charged per NFIP flood-insurance claim record returned from FEMA's NfipClaims dataset.

Examples: 25 claims = $1.26 Β· 100 claims = $5.01 Β· 1,000 claims = $50.01 Β· no matching claims = $0.01.

Coverage note. FEMA publishes redacted claims nationwide; leave state empty to query all of them. Recent claims change as they settle, so payment fields on the newest rows are often 0. Locations are rounded to one decimal place by FEMA.

❓ FAQ

Why did my old runs fail on Oct 21? FEMA removed the v2 endpoint the actor used. The current build reads v3; no input changes are needed.

Why is amountPaidOnBuildingClaim empty? FEMA fills the older paid-amount fields only on settled claims. Use netBuildingPaymentAmount and netContentsPaymentAmount, which are filled on every row.

Can I get addresses or policyholder names? No. FEMA redacts them; only county, ZIP, community and a rounded location are public.

How fresh is the data? FEMA refreshes the dataset regularly; asOfDate on each row shows which refresh it came from.

πŸ†˜ Troubleshooting

  • Run failed with "FEMA data source unavailable" β†’ FEMA's API was down or slow. Retry later; nothing was charged per record.
  • 0 rows β†’ check the state code (two letters) and yearOfLossFrom.
  • Fewer rows than expected β†’ maxResults caps the run; leave it out for up to 1,000.

πŸ€– Use with AI agents

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

Sample agent prompt:

List 2024 NFIP flood claims in Florida with amount paid, flood zone and city.

🏒 About NexGenData β€” public-data actors for research and monitoring. Full catalog: apify.com/nexgendata.

⭐ Found this useful?

If this actor saved you time, please leave a rating on its Store page.