enjoythai.land

Transport

Longdo Place API Thailand taxi POIs.

Thailand-local POI/search layer useful for taxi stands, operator offices, Thai-language place names, address normalization, and nearby search. Use as licensed enrichment alongside OSM, Google, and airport/operator pages.

Commercial Longdo Place API for Thai-local place search, details, reverse geocoding, phone, website, and category data Developer/commercial API; plan and quota depend on Longdo account On demand; weekly/monthly cache refresh for key taxi POIs Open source
Runtime role

Catalog only

Access class

Commercial

Access type

Longdo Place API for Thai-local place search, details, reverse geocoding, phone, website, and category data

Free status

Developer/commercial API; plan and quota depend on Longdo account

Cadence

On demand; weekly/monthly cache refresh for key taxi POIs

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

service or stand name, operator or provider, legal status or certification, vehicle or service category, fare rule where applicable, pickup point or stand, airport terminal/gate where relevant, lat/lon, complaint channel, aggregate trip metrics or demand zone where exposed, quote/ETA fields only when authorized, 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 Thailand taxi and ride-hailing into source-backed decisions: whether a service is legal, what the fare rule actually is, where airport pickup happens, whether a stand or motorcycle-taxi win exists, which areas have strong taxi demand, and which app or complaint surface can actually support the claim.

Endpoint and API notes

Thailand-local POI/search layer useful for taxi stands, operator offices, Thai-language place names, address normalization, and nearby search. Use as licensed enrichment alongside OSM, Google, and airport/operator pages.

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

Developer reference

Best endpoint

Use DLT for legal registry, driver-license, operator-license, Taxi OK/VIP, complaints, and app-certification context; OTP/MOT for aggregate taxi GPS analytics and pickup/dropoff zones; AOT for airport taxi counters and surcharge rules; OSM/Google/Longdo/NOSTRA for stands and pickup points; and platform APIs only where explicit authorization exists.

Recommended refresh

Refresh weekly and record the publication date separately from fetch time.

Travel scoring role

Turns Thailand taxi and ride-hailing into source-backed decisions: whether a service is legal, what the fare rule actually is, where airport pickup happens, whether a stand or motorcycle-taxi win exists, which areas have strong taxi demand, and which app or complaint surface can actually support the claim.

Comparable / backup source

DLT, Thailand.go.th, MOT/OTP, AOT, DLT GPS, OSM/Overpass, Google Places, Longdo, NOSTRA, airport/operator pages, and partner-authorized ride-hailing or fleet integrations.

Example request

# Verify the documented taxi endpoint before production use.
curl -L "https://map.longdo.com/products/api/place" -H "Accept: application/json"

Failure modes

  • There is no single all-taxi Thailand API.
  • Public taxi data is usually aggregate, legal, or airport-specific rather than live dispatch.
  • OTP taxi GPS analytics do not expose raw GPS traces, live vehicle positions, driver identity, or passenger identity.
  • Ride-hailing apps show ETA, fare, and driver data to users, but that does not make it a public ingest API.
  • Airport taxi surcharge, baggage, and toll rules differ from street-hail or app pricing.
  • Motorcycle taxis, metered taxis, airport limousines, and app hire-cars need different service models.
  • Taxi stands and motorcycle-taxi wins are often under-mapped or informal.
  • Complaint datasets are useful for trends, not for realtime operational quality.
  • Dashboard markup or public-page layout can change without notice.
  • Free registration, keys, or rate limits can interrupt automated refresh.
  • Geospatial layers can be large, tiled, or projection-specific.

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.