Catalog only
Tourism and travel
Thailand Tourist Police app.
Public app-information layer for the Thailand Tourist Police application, including emergency assistance, translation, location sharing, alerts, and app-based tourist support context. App-side operational data is not a public bulk API.
Public
Official public app-information page
Free public app
On app-feature or public-service update
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
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
High for official context; validate endpoint availability before automation.
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
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.
Endpoint and API notes
Public app-information layer for the Thailand Tourist Police application, including emergency assistance, translation, location sharing, alerts, and app-based tourist support context. App-side operational data is not a public bulk API.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
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.
Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.
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.
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
# Source landing/download page; inspect linked resources before automation.
curl -L "https://www.touristpolice.go.th/post/tpbnews2025072101"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.
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.