Catalog only
Restaurants, nightlife, and wellness
TAT dining, nightlife, and wellness context.
Useful for official tourism framing around dining neighborhoods, nightlife districts, spa and wellness areas, and visitor-oriented route context. Not a canonical hours, licensing, or live-booking feed.
Public, automation terms unclear
Public tourism website and destination pages for dining districts, nightlife areas, wellness, and spa context
Free public web access; reuse and automated access terms vary by page
Weekly / seasonal / event-driven depending destination page
2026-05-11
Publicly reachable, but automation, bulk reuse, or production SLA terms still need an operator or licensing review.
page reference only
venue name, venue type, cuisine or style, neighborhood or district, lat/lon, address, phone, website, opening hours, business status, ratings or review context where licensed, hotel-area fit, late-return note, source ID
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 restaurants, nightlife, and spas into source-backed decisions about which named venues fit the route, how much return or rain friction exists, what kind of neighborhood the venue lives in, and which source is really proving location, hours, or commercial familiarity.
Endpoint and API notes
Useful for official tourism framing around dining neighborhoods, nightlife districts, spa and wellness areas, and visitor-oriented route context. Not a canonical hours, licensing, or live-booking feed.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use TAT and Thai SELECT for official context, OSM for free venue geometry, Google Places and other licensed POI layers for named venues and hours, and Wongnai-style local discovery only as clearly labeled commercial context.
Refresh weekly and record the publication date separately from fetch time.
Turns restaurants, nightlife, and spas into source-backed decisions about which named venues fit the route, how much return or rain friction exists, what kind of neighborhood the venue lives in, and which source is really proving location, hours, or commercial familiarity.
TAT venue context, Thai SELECT, OSM, Google Places, Wongnai, destination food pages, accommodation pages, taxi and safety layers, and local correction notes once a venue workflow exists.
Example request
# Source landing/download page; inspect linked resources before automation.
curl -L "https://www.tourismthailand.org/"Failure modes
- There is no single public all-venues Thailand API.
- Public tourism pages do not prove current hours, line length, or nightlife mood.
- Commercial POI and review sources have licensing, caching, and pricing limits.
- OpenStreetMap is strong for geometry and fallback logic, but coverage and recency vary by district.
- Nightlife and spa convenience depend heavily on hotel base, late transport, noise, and next-day plans, which pure venue APIs rarely answer.
- Dashboard markup or public-page layout can change without notice.
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.