TripAdvisor Reviews API

Q: Can I filter reviews by language or sort them?

Not in the request: this capability takes only url, with no language or sort setting. Each row carries language, the code TripAdvisor assigns, which can be wrong, so filter on it or on your own detection after you fetch the rows, and sort by posted_at or like_count yourself when order matters.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Pull traveler reviews of a TripAdvisor hotel, restaurant or attraction, with rating, trip type and date, reviewer details and owner responses. Judge freshness by trip_date rather than posted_at, and do not expect every review of the place.

TripAdvisor Reviews reads traveler reviews of one hotel, restaurant or attraction on TripAdvisor, given the place's page link as url. A row holds the title and body of a review, its rating and publish date, when the trip took place and what kind of trip it was, the reviewer's name, handle, home location and number of contributions, and how many likes the review received. Hotels, restaurants and tour operators use it to monitor what visitors say, and analysts use it to compare places or to hand clean review text to a language model for summaries.

Judge freshness by trip_date, the time of the visit, rather than posted_at. Reviews from people with a high author_contributions count are the more credible ones, and trip_type lets you keep the travelers who resemble your own customers. A null like_count means likes are not shown, not that nobody liked the review. The link must point to a single place, not a city page or a list.

Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra TripAdvisor Reviews endpoint (tripadvisor/reviews).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to tripadvisor and action to reviews, and put the parameters inside params.
- Required parameters:
  - url: Target TripAdvisor venue URL for profile and reviews actions, pointing directly to a hotel, restaurant, or attraction listing rather than a city directory.
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, url, title, text, rating, rating_scale, like_count, author_name, author_username, author_location, author_contributions, trip_type; 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=tripadvisor.
- Example request body:
{
  "platform": "tripadvisor",
  "action": "reviews",
  "params": {
    "url": "https://www.tripadvisor.com/AttractionProductReview-g294217-d26810431-Hong_Kong_Street_Food_Tour_with_Locals_Dim_Sum_Wonton_more-Hong_Kong.html"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`tripadvisor`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`reviews`	Capability identifier, fixed value.
`url`	body.params	Not declared	Yes	-	Target TripAdvisor venue URL for `profile` and `reviews` actions, pointing directly to a hotel, restaurant, or attraction listing rather than a city directory. In `profile`, it fetches venue details rather than user profile data.
`limit`	body.params	`integer (1–50)`	No	`20`	The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "tripadvisor",
  "action": "reviews",
  "params": {
    "url": "https://www.tripadvisor.com/AttractionProductReview-g294217-d26810431-Hong_Kong_Street_Food_Tour_with_Locals_Dim_Sum_Wonton_more-Hong_Kong.html"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "tripadvisor",
  "action": "reviews",
  "results": [
    {
      "id": …,
      "url": …,
      "title": …,
      "text": …,
      "rating": …,
      "rating_scale": …,
      "like_count": …,
      "author_name": …,
      "author_username": …,
      "author_location": …,
      "author_contributions": …,
      "trip_type": …,
      "trip_date": …,
      "posted_at": …,
      "language": …,
      "platform": …,
      "owner_response": …,
      "image_urls": …
    }
  ],
  "count": …,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`url`	Link to the record on the platform.
`title`	Title. null when the platform has no titles (for example text-only posts).
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`rating`	Rating. The scale varies by platform: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards.
`rating_scale`	Maximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating.
`like_count`	Likes. null means the platform or this capability does not disclose it; it is not 0.
`author_name`	Author's display name.
`author_username`	Author's username (@handle), usually usable in URLs.
`author_location`	Keeps the platform's own meaning
`author_contributions`	Keeps the platform's own meaning
`trip_type`	Keeps the platform's own meaning
`trip_date`	Keeps the platform's own meaning
`posted_at`	Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
`language`	Content language code (for example zh, en) as judged by the platform; it can be wrong.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
`owner_response`	The business's public reply to this review: text, author_name and posted_at; absent when there is no reply.
`image_urls`	Array of image links in the platform's display order; absent when there are no images.

FAQ

How do I feed TripAdvisor reviews to an AI assistant?

Call this capability from any script, workflow tool or assistant that can send HTTPS requests with your API key, then pass the rows to the model. Each row is structured JSON with title, text, rating, rating_scale and trip_date, and text already has HTML removed, so the model can summarize themes, compare periods or draft replies without cleanup.

Which TripAdvisor page should `url` point to?

The page of one hotel, restaurant or attraction, such as https://www.tripadvisor.com/AttractionProductReview-g294217-d26810431-Hong_Kong_Street_Food_Tour_with_Locals_Dim_Sum_Wonton_more-Hong_Kong.html. City pages and lists of places do not work. To find a place's link from its name, use TripAdvisor Search, Restaurants or Attractions and take the link from a result.

Can I filter reviews by language or sort them?

Not in the request: this capability takes only url, with no language or sort setting. Each row carries language, the code TripAdvisor assigns, which can be wrong, so filter on it or on your own detection after you fetch the rows, and sort by posted_at or like_count yourself when order matters.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).