Place search
1 credit/v1/tripadvisor/searchSearch Tripadvisor places and businesses. Returns PlaceList with url_path values for reviews. Optional location and language.
q, location, language, depth
Tripadvisor APIGet Tripadvisor place review data with one API
Fetch Tripadvisor place search and reviews as structured JSON with one SocialCrawl API key. Shared place and review schema. Reads are priced in credits.
/v1/tripadvisor
2 active endpoints. All standard tier.
- GET /v1/tripadvisor/search
- GET /v1/tripadvisor/reviews
What Tripadvisor endpoints does SocialCrawl ship?
Two live read endpoints for Tripadvisor. Search places, then pull reviews by url_path. Hotels, restaurants, and attractions. Read-only.
Place reviews
1 credit/v1/tripadvisor/reviewsReviews for a Tripadvisor place via url_path from search. Rating, text, author, optional depth and sort.
url_path, depth, sort_by
TripAdvisor API16 endpoints supported
View docsPlaces
Hotels
Restaurants
Attractions
Cruises
Returns TripAdvisor places matching a keyword in a location: name, category, star rating, total review count, and the url_path that identifies the place.
Use it to find a restaurant, hotel, or attraction and get the url_path that the reviews endpoint needs.
1 credit
GET/v1/tripadvisor/search?q=pizza+restaurant&location=New+York%2CNew+York%2CUnited+States
q · Business category, company name, or prominent place (e.g. 'pizza restaurant').
$ curl https://www.socialcrawl.dev/v1/tripadvisor/search?q=pizza+restaurant&location=New+York%2CNew+York%2CUnited+States \
-H "x-api-key: sc_YOUR_API_KEY"idle
// Running this live needs your own API key. Hit "Try it" to see an example responseHow the Tripadvisor API works
Tripadvisor is a normal SocialCrawl data surface. You call GET /v1/tripadvisor/… with an API key, spend credits on live misses, and get a single JSON envelope back.
Authenticate every call
Send your key in the x-api-key header. No Tripadvisor OAuth app for public reads. The same key works across SocialCrawl platforms.
GET with query params
All Tripadvisor routes are GET. Pass q, location, url_path, depth, sort_by, language as query strings. We validate formats before charging.
Pay in credits, not seats
Both routes are standard tier: 1 credit on live miss. Cache hits cost 0. Empty or hard failures refund.
Read one JSON envelope
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.
The usual integration chain
Most products discover entities first, then deepen detail and reviews only when needed.
01Search
GET /v1/tripadvisor/search?q=…PlaceList with url_path values
reviews needs url_path from search.
02Reviews
GET /v1/tripadvisor/reviews?url_path=…ReviewList for the place
Guest language for hotels, restaurants, attractions.
03Locate
GET /v1/tripadvisor/search?q=…&location=…Place hits scoped by location string
Same query differs by city.
04Depth
GET /v1/tripadvisor/reviews?url_path=…&depth=50Larger review window in one call
Depth controls volume without a second product.
request
GET /v1/tripadvisor/search?q=pizza+restaurant&location=New+York,New+York,United+States
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/tripadvisor/reviews?url_path=Hotel_Review-g60763-d23462501-Reviews-…&depth=10response envelope
{
"success": true,
"data": {
"items": [
{
"place": {
"id": "d23462501",
"name": "Example hotel",
"url": "https://www.tripadvisor.com/Hotel_Review-…",
"rating": 4.5
}
}
]
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}What lands in data
Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.
PlaceListsearch
items[] with place name, rating, url_path
ReviewListreviews
items[] with rating, text, author, published_at
Geo-scoped placessearch + location
same PlaceList filtered by location string
Review windowreviews + depth
depth-capped review set
Inside the gateway
Same request lifecycle as every other /v1 platform endpoint. Tripadvisor is not a sidecar.
- 01
Edge receives the call
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
- 02
Validate, then debit
Registry lookup finds tripadvisor/search (or reviews). Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before upstream work.
- 03
Cache or fetch
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: Tripadvisor upstream paths run behind the unified envelope. Retries on 5xx/network with a circuit breaker if the source is unhealthy.
- 04
Normalize and return
Upstream JSON is mapped to commerce archetypes (Product, ProductList, ReviewList, SellerList, App, PlaceList as applicable), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
- search live miss: 1 credit
- reviews live miss: 1 credit
- Cache hit: 0 credits
- Empty / hard fail: auto-refund
- Bad params: 400, never charged
- No credits: 402, never charged
- url_path comes from search
- depth controls review volume
- No booking or owner reply tools
How we get the data
Tripadvisor is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.
What Tripadvisor is for this API
Public places and traveler reviews. Read-only discovery and reputation.
How SocialCrawl reaches it
Tripadvisor upstream paths behind the unified /v1 envelope.
What leaves our edge
PlaceList from search and ReviewList from url_path.
What we do not ship live
No bookings, owner tools, or private messaging.
field map sketch
search hit→ place + url_pathurl_path keys reviews
review rows→ ReviewListrating, text, author
location / language→ query controlsscope search geography and language
What this API is used for
The jobs this API is most often used for.
2active Tripadvisor endpoints in the registry
1 creditper live read on search and reviews
Hospitality and local-business reputation
Callers concentrate on search or taxonomy, then deepen detail and reviews for shortlisted entities. Place search to reviews under one key at 1 credit each. No Tripadvisor partner login.
Live misses are typically a few seconds. Some routes can take longer on cold cache.
What people build with the Tripadvisor API
The jobs Tripadvisor data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Use case examples
Common ways teams put this data to work, and the stack each one tends to run.
Hotel ops
Python, cronsearch brand hotels, reviews for recency checks.
Local SEO teams
Node, sheetssearch by city keyword, sample place ratings and review text.
Travel research
notebookslocation-scoped search then reviews depth for language mining.
Call it in two lines
Standard tier is one credit per live call. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/tripadvisor/search?q=pizza+restaurant&location=New+York,New+York,United+States" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/tripadvisor/reviews?url_path=Hotel_Review-g60763-d23462501-Reviews-Margaritaville_Times_Square-New_York_City_New_York.html&depth=10" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Endpoints
What data does the TripAdvisor API return?
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
SearchSearch TripAdvisor businesses & placesReviewsGet TripAdvisor reviews for a placePlaceGet a TripAdvisor place by URLAutocompleteAutocomplete TripAdvisor placesHotelsSearch TripAdvisor hotelsHotelGet a TripAdvisor hotelRestaurantsSearch TripAdvisor restaurantsRestaurantGet a TripAdvisor restaurantRestaurant ReviewsGet TripAdvisor reviews for a restaurantAttractionsSearch TripAdvisor attractions and things to doAttractionGet a TripAdvisor attractionAttraction ReviewsGet TripAdvisor reviews for an attractionExperience TypesList TripAdvisor experience types for a destinationCruisesSearch TripAdvisor cruisesCruiseGet a TripAdvisor cruise shipCruise ReviewsGet TripAdvisor reviews for a cruise ship
Comparison
How does SocialCrawl compare to Tripadvisor Content API for TripAdvisor data?
Same TripAdvisor data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | Tripadvisor Content API |
|---|---|---|
| Authentication | One x-api-key, sign up and call immediately | Partner application and approval process before access |
| Setup | 16 GET endpoints: search, then reviews via url_path | Access is gated and scoped to approved partner use cases |
| Response schema | Unified PlaceList and ReviewList shared with 64 other platforms | Content API's own format, limited to its exposed fields |
| Pricing | 1 credit per request; 100 free credits, no card | Free tier with call limits; commercial terms for scale |
| Data coverage | Place search plus reviews with photos, owner replies, rating and traveler-type filters, and translation info | Location details with a capped handful of recent reviews per location |
| Maintenance | Task-based sourcing and caching handled server-side for you | You manage keys, quotas, and partner-program compliance |
Authentication
SocialCrawl
One x-api-key, sign up and call immediately
Tripadvisor Content API
Partner application and approval process before access
Setup
SocialCrawl
16 GET endpoints: search, then reviews via url_path
Tripadvisor Content API
Access is gated and scoped to approved partner use cases
Response schema
SocialCrawl
Unified PlaceList and ReviewList shared with 64 other platforms
Tripadvisor Content API
Content API's own format, limited to its exposed fields
Pricing
SocialCrawl
1 credit per request; 100 free credits, no card
Tripadvisor Content API
Free tier with call limits; commercial terms for scale
Data coverage
SocialCrawl
Place search plus reviews with photos, owner replies, rating and traveler-type filters, and translation info
Tripadvisor Content API
Location details with a capped handful of recent reviews per location
Maintenance
SocialCrawl
Task-based sourcing and caching handled server-side for you
Tripadvisor Content API
You manage keys, quotas, and partner-program compliance
FAQ
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I get TripAdvisor data with an API?
SocialCrawl provides 16 TripAdvisor endpoints behind one API key: GET /v1/tripadvisor/search finds hotels, restaurants, and attractions by keyword and location, and GET /v1/tripadvisor/reviews pulls traveler reviews for any place found in search. Both return unified JSON that shares its schema with the other 64 platforms on SocialCrawl.
What data does the SocialCrawl TripAdvisor API return?
Search returns each place's name, category, star rating, total review count, and the url_path used to fetch its reviews. Reviews return the star rating, title, full text, reviewer profile, attached photos, owner or management responses, publish date, and translation info, a translated flag plus the original language.
Do I need an official TripAdvisor Content API key?
No. SocialCrawl handles the data sourcing for you, so there is no TripAdvisor partner application or approval process. You sign up, grab a SocialCrawl API key, and call /v1/tripadvisor/search or /v1/tripadvisor/reviews like any other endpoint.
How much does the TripAdvisor API cost?
Each TripAdvisor request costs 1 credit on the standard tier. New accounts get 100 free credits with no credit card required, and a place with no matching reviews returns a 404 with the credit automatically refunded.
Why do some TripAdvisor API requests take 15–45 seconds?
The upstream data source is task-based rather than instant, so the first request for a given place or query can take roughly 15–45 seconds while results are gathered. SocialCrawl hides the async lifecycle behind an ordinary synchronous request, and repeat requests are served from cache much faster.
Is collecting TripAdvisor data legal?
SocialCrawl returns publicly visible TripAdvisor content: the same place listings and reviews anyone can read on the site, sourced via DataForSEO's Business Data API. You are responsible for ensuring your use case complies with TripAdvisor's terms and applicable data protection laws. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.
What is the best TripAdvisor scraper API?
SocialCrawl covers most TripAdvisor data needs without partner approval: search returns places with ratings and review counts, and the reviews endpoint pulls traveler reviews with photos, owner replies, and translation info, each call for 1 credit. The official Content API requires partner approval and caps reviews per location. 100 free credits, no card.
What is the best TripAdvisor data API?
SocialCrawl is a practical TripAdvisor data API: search finds hotels, restaurants, and attractions with ratings and review counts, and the reviews endpoint pulls traveler reviews with photos, owner replies, and translation info, each for 1 credit. TripAdvisor's official Content API is partner-gated and caps reviews per location, so SocialCrawl gives you broader public place and review data without an approval process, in JSON shared with the other 64 platforms.
Ask AI about SocialCrawl