Bring weather alerts, analysed risk intelligence and early-awareness events into your platform. One secure API. Three connected streams.
/v1/eventsHTTPSGet the breadth to see what is happening, the context to understand it, and the geography to put it on your map.
Official meteorological and disaster warnings for heat, wind, floods, cyclones and other hazards.
weather_alertsFeatureCollectionCurated, analysed risk events enriched with context to support operational decisions.
intelligence_eventsitems[]A broader, lower-latency stream of unanalysed events summarised from open sources.
informative_eventsitems[]Make a GET request with your API key. Receive structured data. Follow the cursor to collect every page.
X-API-Key header. No separate token-generation step.updated_since and resume from your saved watermark.# Your first poll: the last 24 hours
curl --get \
'https://api.intel.datasurfr.ai/v1/events' \
--header "X-API-Key: $DATASURFR_KEY" \
--header 'Accept: application/json' \
--data-urlencode 'limit=100'
# Next polls: add your saved UTC watermark
# --data-urlencode "updated_since=$LAST_SEEN"
# Follow links.next exactly as returned.
# Keep the X-API-Key header on every page.{
"weather_alerts": {
"type": "FeatureCollection",
"count": 0,
"features": []
},
"intelligence_events": { "items": [] },
"informative_events": { "items": [] },
"meta": { "degraded": false, "errors": [] },
"links": { "next": null }
}| Parameter | What it does | Default / range |
|---|---|---|
updated_since | Returns records changed strictly after a timezone-aware ISO-8601 timestamp. | Last 24 hours on first call |
limit | Sets the page size per stream, for up to 3 × limit records per response. | 100 default · 1–500 |
cursor | Continues a page walk. Follow links.next without modifying its URL. | Omit on the first page |
The cursor preserves your time filter. When paging, send only the cursor and limit. Timestamps older than 24 hours are clamped to the rolling window.
A one-time backfill, followed by a predictable polling loop.
Request access from the datasurfr team. Store the key securely on your server and confirm your first response.
Start without updated_since. Follow every links.next URL and upsert records by their stable IDs.
After a complete, non-degraded page walk, save the greatest updated_at value received.
Start a new poll every five minutes using your watermark. Drain all pages before advancing it.
One sequential walker. Predictable delivery. Responses may be cached for 60 seconds. Fetch pages back-to-back within a poll; pace the start of each new poll.
Use the feed as a building block for your own integrations. Your application handles mapping, routing, storage and business rules.
Bring event locations, categories and impact levels into the operational view your team already uses.
Enrich your product with structured weather, analysed intelligence and early-awareness feeds.
Overlay official warning polygons on your own map of sites, routes and areas of interest.
Compare event coordinates and impact radii with your locations to identify potential disruption.
Use your backend to route relevant events into collaboration tools and escalation workflows.
Store the feed in your data platform to build trend views, category analysis and operational reporting.
Clear signals help your application handle partial results, recover from interruptions and keep its position.
Read the technical guideCheck meta.degraded, even on HTTP 200. Process available streams and hold your watermark if any page is degraded.
Upsert by stable record ID. If a cursor is stale, start a fresh walk from your saved watermark within the 24-hour window.
Use exponential backoff on 429 or 503. Log X-Request-ID to help the datasurfr team trace a request.
Tell us what you are building. We’ll help you explore feed access and plan your integration.