Skip to main content
Travel is the primitive for discovering hotels, restaurants, and places across major travel datasets. Use it for destination discovery, hotel comparison, and place research workflows. Google hotel endpoints return live data instantly, while TripAdvisor search uses async task retrieval.
Travel is a use-case view over Business Data — there is no separate /v1/travel route. Every call below maps to a /v1/business/... endpoint (Google Hotels + TripAdvisor). There is no dedicated SDK sub-client; use the CLI (naive business ...) or the Business Data REST/MCP surface.

CLI First

Endpoints

PlatformEndpointDescriptionSpeedCost
Google Hotelshotel-searchesSearch hotels by query + locationLive20 credits
Google Hotelshotel-infoDetailed hotel data (profile/rates/amenities)Live20 credits
TripAdvisorsearchFind places and listingsStandard (async)20 credits

Google Hotels (Live)

Google hotel endpoints return immediate results via:
  • POST /v1/business/google/hotel-searches
  • POST /v1/business/google/hotel-info

Parameters

ParamTypeRequiredDefaultDescription
keywordstringYes (hotel-searches)Hotel search query
hotel_identifierstringYes (hotel-info)Google hotel identifier (CID/place ID)
location_codenumberNoLocation code
language_codestringNoLanguage code
check_instringNoCheck-in date (YYYY-MM-DD)
check_outstringNoCheck-out date (YYYY-MM-DD)
adultsnumberNoNumber of adults

TripAdvisor Search (Async)

TripAdvisor discovery uses async workflow:
  1. Submit via POST /v1/business/tripadvisor/search/task
  2. Check via GET /v1/business/tripadvisor/search/tasks-ready
  3. Retrieve via GET /v1/business/tripadvisor/search/task/:id

Typical Workflow