Severe Alerts
Severe weather alerts, normalized for builders
One versioned API and signed webhooks for multi-region CAP alerts—with keys, quotas, and usage you can meter.
Pipeline
From official feeds to your application
We ingest, normalize, and serve. You query or subscribe.
- 01
Ingest
Severe alerts are pulled from supported national and regional sources and stored in a consistent model.
- 02
Snapshot
A read-optimized snapshot powers the public API—lists, geo queries, and history.
- 03
Deliver
Call REST with an API key, or register HTTPS webhooks for signed push on create/update/cancel.
What you can build against
Designed for server-side integration—not a consumer forecast UI.
Query alerts
List active and historical alerts with filters for country, severity, and event type.
Cursor pagination ·
include=fullfor geometryGeo lookup
Resolve alerts for a point, many points, or a bounding box.
/alerts/by-location,/by-locations,/by-bboxSigned webhooks
Receive HTTPS POSTs when snapshots change. Verify
X-Alert-Signaturewith your endpoint secret.HMAC · delivery history in the dashboard
Account controls
Issue scoped API keys, watch monthly usage, and manage billing in one place.
Keys · usage · Stripe portal
Coverage
Severe alerts for the regions we actively ingest today.
United States, Canada, Europe, Iran, and China. Country codes available live via GET /api/v1/regions.
- AD
- AT
- BA
- BE
- BG
- CA
- CH
- CN
- CY
- CZ
- DE
- DK
- EE
- EI
- ES
- FI
- FR
- GB
- GR
- HR
- HU
- IE
- IL
- IR
- IS
- IT
- JP
- KR
- LT
- LU
- LV
- MD
- ME
- MK
- NL
- NO
- PL
- PT
- RO
- RS
- SE
- SI
- SK
- US
Coverage expands as sources and snapshots grow—treat the regions endpoint as authoritative in the UI when online.
Built for production integrations
Controls you expect from a serious API product.
- API keys & scopes
- Separate keys with
alerts:read,webhooks:write, andusage:read. Revoke anytime. - Rate limits & quotas
- Default fair-use limits (e.g. 60 requests/minute and a monthly quota). Monitor usage in the dashboard.
- Signed webhooks
- Every delivery is HMAC-signed. Invalid or private callback URLs are rejected.
- Versioned HTTP API
- Stable
/api/v1envelope:{ data }on success,{ error: { code, message, details } }on failure. - Open contracts
- Browse docs, download OpenAPI, or import Postman.
Call it like any modern API
Authenticate data-plane requests with your API key.
Verify a webhook
Verify X-Alert-Signature: t=<unix>,v1=<hex> as HMAC_SHA256(secret, "{t}." + raw_body).
curl -s "https://severealert.gcoapps.com/api/v1/alerts/active?per_page=5" \
-H "Authorization: Bearer $SEVERE_ALERTS_API_KEY" \
-H "Accept: application/json"Frequently asked questions
Is this a weather app for end users?
No. Severe Alerts is a developer API for applications that need severe weather alert data.
How do I authenticate?
Create an account, subscribe, then issue an API key. Send Authorization: Bearer <api_key> on data-plane routes. The dashboard uses a separate login token.
Do I need a subscription to call the API?
Yes. Data-plane requests require an active subscription. You’ll get a clear error if one is missing.
What’s the difference between the API and webhooks?
Pull when you need data on your schedule. Webhooks push signed updates when alert snapshots change.
Which regions are supported?
We ingest US, Canada, Europe, Iran, and China. See GET /api/v1/regions for codes present in the live dataset.
Can I filter webhooks?
Yes—optional filters for country, severity, exclude_severity, and event_type.
Where are the docs?
Interactive docs, OpenAPI, and Postman exports are published alongside the API.
Ship weather-aware features without babysitting CAP feeds
Create an account, activate access, and make your first authenticated request.
