Catalog only
Humanitarian and international baselines
ReliefWeb API Thailand.
Humanitarian reports, disasters, jobs, and updates filterable to Thailand.
Public
API
Free public
Real time as content is added
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
hazard type, severity/status, affected area, geometry/layer, timestamp, warning text, sensor/source, update time
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Catalog only
Not yet
No runtime entity scope yet.
No live observation ingestion yet.
Not wired into active decisions yet.
Profiled in the atlas and public pages, but not yet connected to live graph computation.
How this helps travel recommendations
Adds flood, fire, drought, earthquake, tsunami, hotspot, and disaster context when a route, coast, road, or outdoor plan could become unsafe or unrealistic.
Endpoint and API notes
Humanitarian reports, disasters, jobs, and updates filterable to Thailand.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use official disaster feeds, hazard APIs, WMS/WFS layers, or event feeds; keep geometry and severity separate from the text summary.
Refresh every 15-60 minutes, with caching and backoff when the upstream fails.
Adds flood, fire, drought, earthquake, tsunami, hotspot, and disaster context when a route, coast, road, or outdoor plan could become unsafe or unrealistic.
GISTDA, DDPM, GDACS, NASA FIRMS, USGS, TMD earthquake feeds, Thaiwater, and local authority announcements.
Example request
# Verify the documented disaster endpoint before production use.
curl -L "https://reliefweb.int/help/api" -H "Accept: application/json"
Failure modes
- Hazard layers can be geospatial, tiled, or projection-specific.
- Event feeds may lag official local announcements.
- Dashboard-only layers may change markup or token behavior.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.