Tourism and travel

Google Places hotels.

Commercial accommodation POI enrichment for hotel names, place IDs, addresses, maps, ratings, reviews, photos, phone, website, and open-status context where available. Useful for public-facing hotel discovery, not Thai legal hotel registration or live room inventory.

Commercial Google Places APIs for place search, place details, photos, reviews, ratings, and selected accommodation attributes Commercial / pay-as-you-go API On request / event-driven Open source
Runtime role

Catalog only

Access class

Commercial

Access type

Google Places APIs for place search, place details, photos, reviews, ratings, and selected accommodation attributes

Free status

Commercial / pay-as-you-go API

Cadence

On request / event-driven

Last verified

2026-05-11

Access class note

Usually needs payment, partner approval, or a commercial agreement before production use.

Used in layers

page reference only

Useful fields

property or place name, lodging type, neighborhood or area, lat/lon, address, phone, website, star/category signals where available, brand/operator where available, room/rate policy only when authorized, cancellation notes, review/rating context, source ID

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 accommodation into source-backed decisions about the right area to stay, whether the hotel type matches the trip, what transport or flood/noise/AQI friction exists around the base, and which source can actually prove map, legal, or commercial details.

Endpoint and API notes

Commercial accommodation POI enrichment for hotel names, place IDs, addresses, maps, ratings, reviews, photos, phone, website, and open-status context where available. Useful for public-facing hotel discovery, not Thai legal hotel registration or live room inventory.

Open the source endpoint or documentation. Return to the Thailand data atlas.

Developer reference

Best endpoint

Use TAT and official tourism accommodation statistics for destination depth, DBD for operator identity, OSM and Google for map and place enrichment, and commercial partner feeds only when you need live room, rate, cancellation, or inventory fields.

Recommended refresh

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

Travel scoring role

Turns accommodation into source-backed decisions about the right area to stay, whether the hotel type matches the trip, what transport or flood/noise/AQI friction exists around the base, and which source can actually prove map, legal, or commercial details.

Comparable / backup source

TAT, MOTS accommodation statistics, OSM, Google Places, Booking partner data, Agoda context, Open DBD, and local destination pages with explicit source confidence.

Example request

# Verify the documented accommodation endpoint before production use.
curl -L "https://developers.google.com/maps/documentation/places/web-service" -H "Accept: application/json"

Failure modes

  • There is no single public national Thailand hotel-inventory API.
  • Map and review sources do not prove legal operating status or licensing.
  • Legal-entity records do not prove each branch or room product.
  • Rates, cancellation rules, occupancy, and room availability are usually commercial or partner-only data.
  • Flood, AQI, traffic, and nightlife risk are area questions that room-level feeds often do not answer.
  • Dashboard markup or public-page layout can change without notice.
  • 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.