Tripadvisor
Search, listings, detail, reviews, and photos for hotels, restaurants, and attractions from Tripadvisor, served as plain REST.
Endpoints
| Endpoint | Path params | Query params | What it returns | Price | Data up to |
|---|---|---|---|---|---|
GET /tripadvisor/search |
— | query, currency |
Search locations across all content types. | $0.003 | 1 hr |
GET /tripadvisor/home |
— | currency |
Home page feed. | $0.003 | 5 min |
GET /tripadvisor/list |
— | content_type, geo_id, price_min, price_max, amenities, min_rating, sort, update_token, currency |
Listings for hotels, restaurants, or attractions in a location. | $0.003 | 5 min |
GET /tripadvisor/detail |
— | content_type, content_id, currency |
Full detail for one listing. | $0.003 | 5 min |
GET /tripadvisor/reviews |
— | content_type, content_id, min_rating, page_token, currency |
Reviews for one listing, paginated. | $0.003 | 5 min |
GET /tripadvisor/photos |
— | listing_id, offset, currency |
Photos for one listing. | $0.003 | 15 min |
Prices are per call, paid in USDC with x402. "Data up to" is the cache window: a repeated call inside it returns the same data.
Calling it
# x402: no account or API key. The server answers 402 with payment instructions; an x402 client pays and repeats the request.
curl -i "https://<base-url>/tripadvisor/search?query=Bangkok"
Responses are JSON. Field names follow the upstream source, so a response can be larger than the table above suggests.
Notes
content_type(hotel, restaurant, attraction) is a closed enum;min_ratingandsortare free text — Tripadvisor exposes more sort values than any fixed list would safely cover.page_tokenonreviewsis opaque — pass the previous response'snext_page_tokento get the next page, omit it for the first page.
