Tripadvisor hotels in a city

GET https://api.api.sh/tripadvisor/v1/hotels
1 credit / call travel & events try it in the playground →

Hotels in a city or region as Tripadvisor lists them, 30 per page (plus sponsored listings): name, id, URL, rating, review count, ranking, accommodation type, award, price range, lowest price and the booking-site offers for the stay (provider, price, availability, free cancellation), highlighted amenities, AI summary, address, phone, coordinates, neighborhoods and photo, with raw. Without dates the site's default stay is used (default_dates true). total, the applied stay, the sort options and the available filter groups come with the list. Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
locationrequired string City or region: a Tripadvisor geo id (187147), g187147, a Tripadvisor URL containing g<id>, or a place name (the first matching city or region is used; location.resolved_from echoes it). Example: 187147
check_in string Check-in date (YYYY-MM-DD); with check_out. Example: 2026-12-10
check_out string Check-out date (YYYY-MM-DD). Example: 2026-12-12
adults integer Adults (default 2).
rooms integer Rooms (default 1).
sort BEST_VALUE | POPULARITY | PRICE_LOW_TO_HIGH | DISTANCE BEST_VALUE (default), POPULARITY (traveler ranked), PRICE_LOW_TO_HIGH or DISTANCE.
filters string Site filter tokens from Tripadvisor list URLs, comma-separated (max 6), e.g. zfa9 (pets allowed). The available_filters values carry the seo ids.
page integer Page number (30 per page). Pass next_page back as page; null on the last page. Example: 1
domain com | co.uk | de | fr | it | es | in Tripadvisor market: com (default), co.uk, de, fr, it, es or in. Names, prices, currency and review translations follow the market. Default: com

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/tripadvisor/v1/hotels?location=187147" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.