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
| Platform | Endpoint | Description | Speed | Cost |
|---|---|---|---|---|
| Google Hotels | hotel-searches | Search hotels by query + location | Live | 2 credits |
| Google Hotels | hotel-info | Detailed hotel data (profile/rates/amenities) | Live | 2 credits |
| TripAdvisor | search | Find places and listings | Standard (async) | 2 credits |
Google Hotels (Live)
Google hotel endpoints return immediate results via:POST /v1/business/google/hotel-searchesPOST /v1/business/google/hotel-info
Parameters
| Param | Type | Required | Default | Description |
|---|---|---|---|---|
keyword | string | Yes (hotel-searches) | — | Hotel search query |
hotel_identifier | string | Yes (hotel-info) | — | Google hotel identifier (CID/place ID) |
location_code | number | No | — | Location code |
language_code | string | No | — | Language code |
check_in | string | No | — | Check-in date (YYYY-MM-DD) |
check_out | string | No | — | Check-out date (YYYY-MM-DD) |
adults | number | No | — | Number of adults |
TripAdvisor Search (Async)
TripAdvisor discovery uses async workflow:- Submit via
POST /v1/business/tripadvisor/search/task - Check via
GET /v1/business/tripadvisor/search/tasks-ready - Retrieve via
GET /v1/business/tripadvisor/search/task/:id