When a wildfire tears through a community or a hurricane leaves a town underwater, the last thing residents need is your promotion in their inbox. Zipawa is a real-time API that gives your systems the full event context for every ZIP code — what's coming, what's happening, and what communities are recovering from — so you decide: suppress, pause, or reach out to help.
Built for the platforms your campaigns already run on
Your automation doesn't watch the weather. It happily mails a home-insurance upsell into a neighborhood that burned down last week, or pushes a flash sale into a town still pumping floodwater out of its basements. Customers don't blame the algorithm — they blame you.
"Protect your home today!" delivered to a street where half the homes are gone. Screenshot, viral post, PR crisis.
A flash-sale alert lands while families are tracking a tornado warning for their own neighborhood. Unsubscribes spike. Trust craters.
Evacuated households aren't shopping. Suppressing impacted ZIPs isn't just respectful — it's better ROAS.
Every county with active event context, colored by severity — straight from our data, refreshed every 15 minutes. This is the county-level teaser; the API returns it down to the ZIP.
Our pipeline automatically ingests multiple official government feeds — including NWS weather alerts, FEMA disaster declarations, USGS earthquakes, and IPAWS emergency alerts — refreshed every 15 minutes.
Every event is geocoded to the ZIP codes it affects, categorized, scored for severity, classified by timing — forecast, active, or aftermath — and given a time window with a start, a decay, and an expiry.
One API call before every send, drop, or dial. Pass a ZIP list, get the full context back, and filter it to fit your playbook — suppress the aftermath, pause during the storm, or send prep messaging ahead of it. Integrates with any campaign stack in an afternoon.
Filter to the categories that matter to your industry. A home-services brand and a travel app don't need the same suppression rules — so you choose.
Active fires, evacuation zones, and smoke-impact areas.
Landfall zones, surge flooding, and recovery windows.
Touchdown paths, damage corridors, hail and wind events.
Riverine and flash flooding with affected drainage areas.
Extreme heat advisories and air-quality alerts affecting vulnerable residents.
Shake-intensity zones and aftershock advisory periods.
Ice storms, blizzards, and extended freeze events.
Your own suppression zones — added via the admin console or API.
A flood recedes in days; the recovery it leaves behind takes months. Every Zipawa event carries a full lifecycle — onset, peak, decay, and expiry — so suppression lifts automatically when it's appropriate, not when someone remembers to clean up a list.
REST + JSON with predictable schemas. Two endpoints: /v1/events returns the full context so your rules decide; /v1/suppressions is the opinionated shortcut when you just want to know where not to market.
No code? Use Zipawa inside Claude →
// 200 OK — full context; your filters, your call
{
"as_of": "2026-06-11T14:02:11Z",
"filters": { "timing": ["aftermath"], "min_severity": "high" },
"zips": [
{
"zip": "93534",
"events": [
{
"event_id": "evt_8x2kq",
"category": "wildfire",
"severity": "critical",
"timing": "aftermath",
"title": "Eaton Ridge Fire — community recovery",
"window": {
"starts_at": "2026-06-07T03:15:00Z",
"expires_at": "2026-07-22T00:00:00Z",
"phase": "decay"
}
}
]
},
{ "zip": "33401", "events": [] }
]
}Scrub mail files before every drop. Long print lead times make stale lists dangerous — screen at print and at delivery scheduling.
Add a suppression check to your send pipeline. Pause geo-targeted journeys automatically when an event is flagged.
Pause acquisition campaigns in disaster zones while claims teams engage — the same event data can route both decisions.
Nothing reads worse than "We buy houses!" in a burn zone. Suppress prospecting in impacted neighborhoods automatically.
A hurricane is forecast: send preparation notices to customers in its path. Lines down afterward: switch to outage support. Same API, different timing filter.
Swap promotional creative for support messaging in impacted areas — or go quiet entirely. Your call, our signal.
Full API access to test and integrate. No credit card required.
For marketing teams running always-on, multi-channel campaigns.
For platforms, agencies, and brands protecting many clients at once.
Always free — no credit card, full API access, and every category we monitor across multiple federal data sources.