enjoythai.land

Law, politics, and civic

ACLED Thailand.

Political violence, demonstrations, protest, and conflict-event data.

Free registration API/export Free registration for many uses Regular Open source
Runtime role

Catalog only

Access class

Free registration

Access type

API/export

Free status

Free registration for many uses

Cadence

Regular

Last verified

2026-05-11

Access class note

Publicly reachable, but account creation, an API key, or registration flow may be required.

Used in layers

page reference only

Useful fields

agency, station or office type, hotline, address, coordinates, province/district, case group, reported and arrested counts, crash deaths and injuries, alert severity, EMS summary fields, privacy level, source confidence, last verified

Reliability rating

Medium-high for discovery and context; operational reliability depends on endpoint stability.

Runtime truth

Runtime role

Catalog only

Production ready

Not yet

Entity scope

No runtime entity scope yet.

Observation scope

No live observation ingestion yet.

Decision scope

Not wired into active decisions yet.

Runtime note

Profiled in the atlas and public pages, but not yet connected to live graph computation.

How this helps travel recommendations

Turns safety data into source-backed decisions about emergency numbers, nearest police or tourist-police access, road-crash risk, ambulance and 1669 expectations, disaster overlays, wildfire or protest caution, and what kind of safety signal a page is really using.

Developer reference

Best endpoint

Use Royal Thai Police and police-station datasets for station and hotline truth, Tourist Police for traveler help channels, ThaiRSC and PRS for road-safety dashboards, NIEMS for EMS and 1669 context, DDPM or GISTDA for disaster and fire layers, and treat OSM only as emergency POI enrichment.

Recommended refresh

Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.

Travel scoring role

Turns safety data into source-backed decisions about emergency numbers, nearest police or tourist-police access, road-crash risk, ambulance and 1669 expectations, disaster overlays, wildfire or protest caution, and what kind of safety signal a page is really using.

Comparable / backup source

Royal Thai Police, GDC police-station datasets, Tourist Police, ThaiRSC, PRS, NIEMS, DDPM, BMA fire-station data, GISTDA, DNP, NASA FIRMS, ACLED, GDELT, NSO, UNODC, World Bank, and OSM emergency POIs.

Example request

# Verify the documented safety endpoint before production use.
curl -L "https://acleddata.com/" -H "Accept: application/json"

Failure modes

  • There is no public realtime national emergency-dispatch API for police, fire, or ambulance in Thailand.
  • Reported crime statistics describe reported or processed cases, not the full underlying incidence.
  • Cybercrime is overrepresented in public police open data compared with many other crime types.
  • Road-accident data is stronger and more current than general-crime data, so safety pages need to say which risk they are actually showing.
  • Tourist-police app functions and live incident handling are operational, not a public bulk feed.
  • Case-level victims, officer locations, patient details, and emergency-call data are restricted and should not be inferred from public dashboards.
  • Free registration, keys, or rate limits can interrupt automated refresh.

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.