SourceFinch Verified · Grants & public funding

FEMA hazard mitigation grant subapplications

Hazard Mitigation Assistance subapplications (HMGP, BRIC, FMA and related programs) most recently submitted to FEMA, with applicant, state, counties, hazard, status, requested federal share and amounts obligated and paid.

Monitor this sourceAPI, CLI, SDK and MCP

What changed300 changes in 7 days, latest

At a glance

Jurisdiction
United States (federal)
Publisher updates
Refreshed by FEMA daily
Recommended schedule
Daily for your monitor; SourceFinch verifies the recipe daily
Records per run
25 in the latest run
Record key
id
Acquired from
Publisher's public API: https://www.fema.gov/api/open/v2/HmaSubapplications?$filter=dateSubmittedToFema%20gt%20%272000-01-01T00:00:00.000z%27%20and%20dateSubmittedToFema%20lt%20%272100-01-01T00:00:00.000z%27&$orderby=dateSubmittedToFema%20desc,id&$top=25
Recipe
v2.0.0, approved October 19, 2026
Version notes
FEMA retired the Hazard Mitigation Assistance Projects v4 dataset on 2026-10-15 and combined it into HMA Subapplications v2, so version 1.0.0 returns no records. Version 2.0.0 reads the 25 subapplications most recently submitted to FEMA from the new dataset. The fields change with the dataset: the record key is still id, but project_identifier becomes subapplication_identifier, program_area becomes program, state and county become subapplicant_state and benefiting_counties, subrecipient becomes subapplicant_name, project_type becomes subapplication_type, project_amount becomes total_subapplication_amount, federal_share_obligated becomes total_obligated_amount, and date_approved is replaced by date_submitted_to_fema because the new dataset has no approval date. New: applicant_name, fiscal_year, region, subapplicant_state_abbreviation, disaster_number, primary_activity, primary_hazard, federal_share_amount and total_payment_amount.
Verified since
October 19, 2026
Last green run
November 17, 2026
Changes, last 7 days
300 · see what changed

What the data contains

Subapplications for FEMA's Hazard Mitigation Assistance grant programs: the Hazard Mitigation Grant Program (HMGP), Building Resilient Infrastructure and Communities (BRIC), Flood Mitigation Assistance (FMA) and HMGP Post Fire. Data comes from the OpenFEMA HMA Subapplications dataset (version 2), which FEMA combined with and replaced the Hazard Mitigation Assistance Projects dataset (version 4) on 2026-10-15. Each record is one subapplication: its identifier, program and fiscal year, FEMA region, applicant (usually a state emergency management agency) and subapplicant (a local government, tribe, utility or public body), state and benefiting counties, disaster number, subapplication type and primary activity and hazard, current status, the date it was submitted to FEMA, the federal share requested or approved, the total subapplication amount and the amounts obligated and paid so far. Each run reads the 25 subapplications most recently submitted to FEMA, so a monitor reports new submissions and later changes to their status, obligations and payments as FEMA reviews, approves and funds them. Amounts are in U.S. dollars as reported by FEMA from its grants systems, not from its official financial systems, and FEMA notes they may differ slightly from USAspending.gov; a few historical rows carry placeholder submission dates, which the query excludes. FEMA removes personal information before publication. OpenFEMA's citation and non-endorsement statement travels with every record.

Fields and types

Every record has these fields. The key field id identifies a record across runs, so changes are reported field by field.

FieldTypeDescription
idkeystringOpenFEMA's unique identifier for the subapplication row. The record key.
subapplication_identifierstringFEMA subapplication identifier, usually the disaster or grant number plus a sequence (for example DR-4812-0008).
programstringGrant program name as reported by FEMA: Hazard Mitigation Grant Program, Hazard Mitigation Grant Program Post Fire, Building Resilient Infrastructure and Communities or Flood Mitigation Assistance.
fiscal_yearintegerFederal fiscal year of the grant program funding opportunity.
regionintegerFEMA region number (1 to 10) of the subapplication.
applicant_namestringApplicant (recipient) requesting the grant, typically a state, territory or tribal emergency management agency.
subapplicant_namestringSubapplicant (subrecipient) that carries out the work, typically a local government, tribe, utility or public body, as FEMA reports it.
subapplicant_statestringFull name of the subapplicant's state, territory or tribal area.
subapplicant_state_abbreviationstringTwo-letter abbreviation of the subapplicant's state or territory.
benefiting_countiesstring, nullableCounty or county-equivalent the subapplication benefits; several counties are separated by commas, and statewide work is marked Statewide.
disaster_numberstring, nullableFEMA disaster declaration number the subapplication is funded under, when it follows a declaration.
subapplication_typestringType of subapplication: Project, Plan, Project scoping, Management cost, Technical assistance, 5% initiative, or Pending until FEMA classifies it.
primary_activitystring, nullablePrimary mitigation activity, for example Acquisition, Elevation, Flood control or Management costs.
primary_hazardstring, nullablePrimary hazard the subapplication mitigates, for example Flood, Tornado, Windstorms or Wildfire.
statusstringCurrent status in FEMA's grants system, for example Pending, Submitted to FEMA, Approved, Closed or Void.
date_submitted_to_femadatetimeDate the subapplication was submitted to FEMA (ISO 8601). Runs read the 25 most recent.
federal_share_amountnumber, nullableFederal cost share requested or approved for the subapplication, in U.S. dollars.
total_subapplication_amountnumber, nullableTotal amount requested or approved for the subapplication, in U.S. dollars.
total_obligated_amountnumber, nullableTotal federal amount obligated so far, in U.S. dollars; empty until FEMA obligates funds.
total_payment_amountnumber, nullableTotal paid to the recipient so far, in U.S. dollars; empty until a payment is made.

Sample output

The first 5 of 25 records from SourceFinch's own run on November 17, 2026, exactly as delivered.

FieldRecord 1Record 2Record 3Record 4Record 5
id010389d7-3a46-484b-8694-531aadf89b7e71cacfa5-a9fe-487f-a25b-85775bfd8b54873394f6-b261-49f2-a8b0-1d3f637cee1b3990ab20-6b05-4654-a939-90ffe1e7cebd062e241f-caf0-45bb-89b9-e2885fd7aedb
subapplication_identifierDR-4498-0032-RDR-4498-0031-FEMA-2024-SW-007-0001EMA-2024-SW-007-0003EMT-2024-SW-003-0002
programHazard Mitigation Grant ProgramHazard Mitigation Grant ProgramFlood Mitigation Assistance Swift CurrentFlood Mitigation Assistance Swift CurrentFlood Mitigation Assistance Swift Current
fiscal_year20202020202420242024
region88446
applicant_nameStatewideStatewideKENTUCKY DEPARTMENT OF MILITARY AFFAIRSKENTUCKY DEPARTMENT OF MILITARY AFFAIRSOK DEPT OF EMERGENCY MGMT
subapplicant_nameCrestoneColorado SpringsDIVISION OF EMERGENCY MANAGEMENTCOUNTY OF CLARKOK DEPT OF EMERGENCY MGMT
subapplicant_stateColoradoColoradoKentuckyKentuckyOklahoma
subapplicant_state_abbreviationCOCOKYKYOK
benefiting_countiesSaguacheEl PasoJEFFERSON COUNTY; CLARK COUNTYCLARK COUNTYOKLAHOMA COUNTY; POTTAWATOMIE COUNTY; MCCLAIN COUNTY; CANADIAN COUNTY; CLEVELAND COUNTY; TULSA COUNTY
disaster_number44984498———
subapplication_typeProject5% initiativeManagement costProjectManagement cost
primary_activityWildfire managementWildfire managementManagement costsElevationManagement costs
primary_hazardFireFire—Flooding—
statusWithdrawnWithdrawnSubmitted to FEMASubmitted to FEMASubmitted to FEMA
date_submitted_to_fema2026-11-10T00:00:00.000Z2026-11-10T00:00:00.000Z2026-11-09T00:00:00.000Z2026-11-02T00:00:00.000Z2026-10-30T00:00:00.000Z
federal_share_amount00262248.71314962.66435679
total_subapplication_amount00268973.04317236.66435679
total_obligated_amount—————
total_payment_amount—————
Sample as JSON
[
  {
    "id": "010389d7-3a46-484b-8694-531aadf89b7e",
    "region": 8,
    "status": "Withdrawn",
    "program": "Hazard Mitigation Grant Program",
    "fiscal_year": 2020,
    "applicant_name": "Statewide",
    "primary_hazard": "Fire",
    "disaster_number": "4498",
    "primary_activity": "Wildfire management",
    "subapplicant_name": "Crestone",
    "subapplicant_state": "Colorado",
    "benefiting_counties": "Saguache",
    "subapplication_type": "Project",
    "federal_share_amount": 0,
    "total_payment_amount": null,
    "date_submitted_to_fema": "2026-11-10T00:00:00.000Z",
    "total_obligated_amount": null,
    "subapplication_identifier": "DR-4498-0032-R",
    "total_subapplication_amount": 0,
    "subapplicant_state_abbreviation": "CO"
  },
  {
    "id": "71cacfa5-a9fe-487f-a25b-85775bfd8b54",
    "region": 8,
    "status": "Withdrawn",
    "program": "Hazard Mitigation Grant Program",
    "fiscal_year": 2020,
    "applicant_name": "Statewide",
    "primary_hazard": "Fire",
    "disaster_number": "4498",
    "primary_activity": "Wildfire management",
    "subapplicant_name": "Colorado Springs",
    "subapplicant_state": "Colorado",
    "benefiting_counties": "El Paso",
    "subapplication_type": "5% initiative",
    "federal_share_amount": 0,
    "total_payment_amount": null,
    "date_submitted_to_fema": "2026-11-10T00:00:00.000Z",
    "total_obligated_amount": null,
    "subapplication_identifier": "DR-4498-0031-F",
    "total_subapplication_amount": 0,
    "subapplicant_state_abbreviation": "CO"
  },
  {
    "id": "873394f6-b261-49f2-a8b0-1d3f637cee1b",
    "region": 4,
    "status": "Submitted to FEMA",
    "program": "Flood Mitigation Assistance Swift Current",
    "fiscal_year": 2024,
    "applicant_name": "KENTUCKY DEPARTMENT OF MILITARY AFFAIRS",
    "primary_hazard": null,
    "disaster_number": null,
    "primary_activity": "Management costs",
    "subapplicant_name": "DIVISION OF EMERGENCY MANAGEMENT",
    "subapplicant_state": "Kentucky",
    "benefiting_counties": "JEFFERSON COUNTY; CLARK COUNTY",
    "subapplication_type": "Management cost",
    "federal_share_amount": 262248.71,
    "total_payment_amount": null,
    "date_submitted_to_fema": "2026-11-09T00:00:00.000Z",
    "total_obligated_amount": null,
    "subapplication_identifier": "EMA-2024-SW-007-0001",
    "total_subapplication_amount": 268973.04,
    "subapplicant_state_abbreviation": "KY"
  },
  {
    "id": "3990ab20-6b05-4654-a939-90ffe1e7cebd",
    "region": 4,
    "status": "Submitted to FEMA",
    "program": "Flood Mitigation Assistance Swift Current",
    "fiscal_year": 2024,
    "applicant_name": "KENTUCKY DEPARTMENT OF MILITARY AFFAIRS",
    "primary_hazard": "Flooding",
    "disaster_number": null,
    "primary_activity": "Elevation",
    "subapplicant_name": "COUNTY OF CLARK",
    "subapplicant_state": "Kentucky",
    "benefiting_counties": "CLARK COUNTY",
    "subapplication_type": "Project",
    "federal_share_amount": 314962.66,
    "total_payment_amount": null,
    "date_submitted_to_fema": "2026-11-02T00:00:00.000Z",
    "total_obligated_amount": null,
    "subapplication_identifier": "EMA-2024-SW-007-0003",
    "total_subapplication_amount": 317236.66,
    "subapplicant_state_abbreviation": "KY"
  },
  {
    "id": "062e241f-caf0-45bb-89b9-e2885fd7aedb",
    "region": 6,
    "status": "Submitted to FEMA",
    "program": "Flood Mitigation Assistance Swift Current",
    "fiscal_year": 2024,
    "applicant_name": "OK DEPT OF EMERGENCY MGMT",
    "primary_hazard": null,
    "disaster_number": null,
    "primary_activity": "Management costs",
    "subapplicant_name": "OK DEPT OF EMERGENCY MGMT",
    "subapplicant_state": "Oklahoma",
    "benefiting_counties": "OKLAHOMA COUNTY; POTTAWATOMIE COUNTY; MCCLAIN COUNTY; CANADIAN COUNTY; CLEVELAND COUNTY; TULSA COUNTY",
    "subapplication_type": "Management cost",
    "federal_share_amount": 435679,
    "total_payment_amount": null,
    "date_submitted_to_fema": "2026-10-30T00:00:00.000Z",
    "total_obligated_amount": null,
    "subapplication_identifier": "EMT-2024-SW-003-0002",
    "total_subapplication_amount": 435679,
    "subapplicant_state_abbreviation": "OK"
  }
]

Evidence behind every value

  • Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash b33c000880e413453811b669b0a12b9c4313bbc7915ab84d3f7faa4e0f54b267.
  • Every value records where it came from in that response: a JSON Pointer into the retained capture.
  • Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is 595bcc5ec13b92c0103861ddaea2d2e2c76dd286599a754c276dcb08b8ffb994, timestamped November 17, 2026.
  • The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
  • Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch: sourcefinch verify-bundle run.wacz.

Terms posture and usage rights

Terms
Automated access permitted · publisher's terms
robots.txt
Allows this path · SHA-256 0d0ff477a1a86c3e…
AI-preference signals
None observed at review
Public record
Yes. Hazard mitigation grants are federal awards under the Stafford Act (42 U.S.C. 5133, 5170c) and the National Flood Insurance Act (42 U.S.C. 4104c); FEMA publishes the project data as open data.
Reviewed
October 19, 2026; next review April 19, 2027
Licence basis
Publisher's terms of use
Commercial use
Allowed with conditions
Redistribution
Allowed with conditions
Attribution
Required (text below)

OpenFEMA offers FEMA's public data through an API without a key. Its terms require citing the dataset and the access date, stating that the product uses the OpenFEMA API but is not endorsed by FEMA, not modifying the data while presenting it as FEMA's, not using FEMA or DHS logos, not attempting to re-identify individuals, and using the data for statistical research or as a reporting record rather than for decisions about individuals' rights or benefits.

Federal Emergency Management Agency (FEMA), OpenFEMA Dataset: HMA Subapplications - v2. This product uses the FEMA OpenFEMA API, but is not endorsed by FEMA. The Federal Government or FEMA cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s).

Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.

Reliability

Runs, last 30 days
29
Green
96.6%
Failed
1
Median run time
1.0 s
Latest run
success, November 17, 2026

Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: October 19, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.

Use it

Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).

Console

Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.

Portable recipe

Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.

{
  "schema": "sourcefinch/source@1",
  "name": "FEMA hazard mitigation grant subapplications",
  "url": "https://www.fema.gov/api/open/v2/HmaSubapplications?$filter=dateSubmittedToFema%20gt%20%272000-01-01T00:00:00.000z%27%20and%20dateSubmittedToFema%20lt%20%272100-01-01T00:00:00.000z%27&$orderby=dateSubmittedToFema%20desc,id&$top=25",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "HmaSubapplications[*]",
    "fields": {
      "id": "id",
      "region": "region",
      "status": "status",
      "program": "program",
      "fiscal_year": "fiscalYear",
      "applicant_name": "applicantName",
      "primary_hazard": "primaryHazard",
      "disaster_number": "disasterNumber",
      "primary_activity": "primaryActivity",
      "subapplicant_name": "subapplicantName",
      "subapplicant_state": "subapplicantState",
      "benefiting_counties": "benefitingCounties",
      "subapplication_type": "subapplicationType",
      "federal_share_amount": "federalShareAmount",
      "total_payment_amount": "totalPaymentAmount",
      "date_submitted_to_fema": "dateSubmittedToFema",
      "total_obligated_amount": "totalObligatedAmount",
      "subapplication_identifier": "subapplicationIdentifier",
      "total_subapplication_amount": "totalSubapplicationAmount",
      "subapplicant_state_abbreviation": "subapplicantStateAbbreviation"
    },
    "required": [
      "id",
      "subapplication_identifier",
      "status",
      "date_submitted_to_fema"
    ]
  },
  "schedule": "daily",
  "key_field": "id"
}

source.json

The request body used by the API, CLI and SDK examples.

{
  "name": "FEMA hazard mitigation grant subapplications",
  "url": "https://www.fema.gov/api/open/v2/HmaSubapplications?$filter=dateSubmittedToFema%20gt%20%272000-01-01T00:00:00.000z%27%20and%20dateSubmittedToFema%20lt%20%272100-01-01T00:00:00.000z%27&$orderby=dateSubmittedToFema%20desc,id&$top=25",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "HmaSubapplications[*]",
    "fields": {
      "id": "id",
      "region": "region",
      "status": "status",
      "program": "program",
      "fiscal_year": "fiscalYear",
      "applicant_name": "applicantName",
      "primary_hazard": "primaryHazard",
      "disaster_number": "disasterNumber",
      "primary_activity": "primaryActivity",
      "subapplicant_name": "subapplicantName",
      "subapplicant_state": "subapplicantState",
      "benefiting_counties": "benefitingCounties",
      "subapplication_type": "subapplicationType",
      "federal_share_amount": "federalShareAmount",
      "total_payment_amount": "totalPaymentAmount",
      "date_submitted_to_fema": "dateSubmittedToFema",
      "total_obligated_amount": "totalObligatedAmount",
      "subapplication_identifier": "subapplicationIdentifier",
      "total_subapplication_amount": "totalSubapplicationAmount",
      "subapplicant_state_abbreviation": "subapplicantStateAbbreviation"
    },
    "required": [
      "id",
      "subapplication_identifier",
      "status",
      "date_submitted_to_fema"
    ]
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "openfema-hazard-mitigation-projects",
    "version_id": "32470090-cb00-424d-829e-cf05c4a472b2"
  }
}

REST API

Create an API key under Console → API keys. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/openfema-hazard-mitigation-projects -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

CLI

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get openfema-hazard-mitigation-projects --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

TypeScript SDK

The SDK is not on npm yet; see /docs/sdk.

import { SourceFinch } from "@sourcefinch/sdk";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("openfema-hazard-mitigation-projects");
const source = await sf.sources.create({
  catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

MCP

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor FEMA hazard mitigation grant subapplications: get_catalog_source openfema-hazard-mitigation-projects,
then create_source with its create_source_args (dry run first), then run_source."

Pricing

Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.

More from Federal Emergency Management Agency (FEMA) and in grants & public funding.

SourceFinch is independent and is not affiliated with or endorsed by Federal Emergency Management Agency (FEMA). This page describes fema hazard mitigation grant subapplications as SourceFinch acquires it.