enjoythai.land

Transport

Booking.com Demand API car rentals.

Real-time car-rental inventory, availability, pricing, depot, supplier, and booking functionality through Booking.com Demand API Cars. Use for live quote and booking flows only when authorized.

Commercial Partner API documentation for content, search, redirect, booking, depots, suppliers, details, and reporting flows Partner authorization required; API credentials and commercial terms apply On request for quotes and availability; static docs on product change Open source
Runtime role

Catalog only

Access class

Commercial

Access type

Partner API documentation for content, search, redirect, booking, depots, suppliers, details, and reporting flows

Free status

Partner authorization required; API credentials and commercial terms apply

Cadence

On request for quotes and availability; static docs on product change

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

supplier, legal entity, branch/depot, airport terminal/floor/gate, depot type, lat/lon, vehicle class, ACRISS code, rate, taxes/fees, deposit, excess, insurance, IDP/license rule, pickup/dropoff rules, booking channel, 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 vehicle rental into source-backed decisions: whether the company legally exists, where pickup actually happens, whether the offer is self-drive or with-driver, what insurance/deposit terms apply, whether a motorcycle needs separate license logic, and which layer can actually prove live availability.

Developer reference

Best endpoint

Use Open DBD for legal rental-company identity, DLT for vehicle/license macro context, OCPB for controlled-contract rules, BOT for long-term leasing boundaries, AOT for airport counters, Booking/Expedia/Sabre/Amadeus/CarTrawler/Skyscanner for live offers where authorized, and OSM/Google/Longdo/NOSTRA for branch or shop enrichment.

Recommended refresh

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

Travel scoring role

Turns Thailand vehicle rental into source-backed decisions: whether the company legally exists, where pickup actually happens, whether the offer is self-drive or with-driver, what insurance/deposit terms apply, whether a motorcycle needs separate license logic, and which layer can actually prove live availability.

Comparable / backup source

Open DBD, DLT, OCPB, BOT, AOT, Drivehub, Drivemate, OSM/Overpass, Google Places, Longdo, NOSTRA, OIC, MOT road-accident datasets, ThaiRSC, and supplier/airport pages.

Example request

# Verify the documented rental endpoint before production use.
curl -L "https://developers.booking.com/demand/docs/cars/overview" -H "Accept: application/json"

Failure modes

  • There is no single all-rental Thailand API.
  • A legal company record does not prove every branch, airport desk, or vehicle in stock.
  • Airport counter pages show presence, not live availability or confirmed booking inventory.
  • Motorcycle rental, self-drive car rental, with-driver services, peer rental, and long-term leasing need separate service models.
  • Commercial booking APIs are the only reliable source for live rates, deposit, excess, and one-way fee fields.
  • A vehicle class or ACRISS code often means 'or similar', not a guaranteed exact model.
  • Compulsory insurance does not equal full rental protection, and contract fairness does not prove broad coverage.

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.