Trip.com Hotels Scraper

Trip.com Hotels Scraper collects public hotel listings from destination pages into a dataset for travel research and inventory comparisons. Get hotel names, links, available ratings, review counts and visible prices, then export the results or use them from your own application. It reads the supplied listing page, not every page of a destination or hotel room details.

Quick start

1. Copy a public Trip.com destination hotel-list URL.
2. Paste it into Trip.com hotel list URLs and start with a small maximum.
3. Run the Actor, then open its dataset to review and export the hotel rows.

{
  "searchUrls": [
    {
      "url": "https://www.trip.com/hotels/tokyo-hotels-list-228/"
    }
  ],
  "maxItems": 20
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose an example to start with a preconfigured destination input.

• Rio de Janeiro hotels — Collect public hotel listings for a Brazilian destination.
• Lisbon hotels — Review public hotel inventory in Lisbon.
• Edinburgh hotels — Collect an additional European destination listing.

What you get

• One row per distinct hotel found on the supplied pages, up to maxItems across the run.
• Hotel name, detail URL and parsed hotel ID when available.
• Available star and guest ratings, review counts, images and location text.
• Visible card prices and detected currencies when present. Prices are not guaranteed total-stay quotes.
• Source URLs, collection timestamps and completeness warnings.

The key-value store also contains RUN_SUMMARY with saved counts, source errors, skipped invalid URLs with correction guidance, and pending URLs. This is separate from the hotel dataset.

Who is it for?

• Travel analysts comparing destination hotel inventory.
• Hotel teams reviewing nearby properties and publicly visible ratings.
• Agencies preparing travel research tables.
• Developers adding public hotel listing records to a data workflow.

Input settings

Setting	JSON key	Behavior
Hotel list URLs	searchUrls	Required in the form. Up to 50 public HTTPS hotel-list URLs.
Stay dates	checkIn, checkOut	Supply both in YYYY-MM-DD format or omit both.
Guests and rooms	adults, rooms	Defaults to 2 adults and 1 room. Added to URLs only when dates are supplied.
Maximum hotels	maxItems	Defaults to 20 across all sources. Range 1–10,000.
Work budget	maxRuntimeSecs	Defaults to 270 seconds.
Safety margin	runtimeSafetySecs	Defaults to 30 seconds. Must be lower than the work budget.
Connection settings	proxyConfiguration	Optional explicit proxy settings. Omitted input uses direct access.

Use hotel listing URLs such as the Tokyo URL in Quick start, not the Trip.com homepage or things-to-do/attraction pages. For Lisbon hotels, use https://www.trip.com/hotels/lisbon-hotels-list-1231/. Invalid source URLs are skipped with a visible warning and recorded in RUN_SUMMARY.skippedSources; valid hotel sources in the same batch continue normally. When every source URL is invalid, the run succeeds with an empty dataset, an EMPTY summary, and no custom start or item charge or network request. The URL shown in the form is a prefill, not an API default. API callers must supply their own URL list.

For a date-specific recipe, add both checkIn and checkOut. Choose a checkout later than check-in. Dates are forwarded to Trip.com and do not guarantee that the returned public response contains prices.

Output data

Fields	Meaning
hotelName, hotelUrl, hotelId	Public hotel identity and available detail link.
destination, district, address	Location text when present on the listing.
starRating, guestRating, reviewCount	Available hotel ratings and review totals, not review text.
price, currency, taxesFeesText	Visible card price and accompanying tax/fee wording when available.
imageUrl	Hotel image URL when available.
amenities	Reserved array. Currently returned empty.
sourceUrl, resultPage, scrapedAt	Requested source, page number (currently 1) and collection time.
status, warning	SAVED for hotel rows and any completeness note.

Missing optional values are null. Structured-data results can contain fewer fields than visible listing cards.

Synthetic shape-only example, not a measured hotel or price:

{
  "hotelName": "Example hotel",
  "hotelUrl": null,
  "hotelId": null,
  "destination": null,
  "district": null,
  "starRating": null,
  "guestRating": null,
  "reviewCount": null,
  "price": null,
  "currency": null,
  "taxesFeesText": null,
  "amenities": [],
  "imageUrl": null,
  "address": null,
  "sourceUrl": "https://www.trip.com/hotels/tokyo-hotels-list-228/",
  "resultPage": 1,
  "status": "SAVED",
  "warning": null,
  "scrapedAt": "2026-10-26T00:00:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing. The start event is charged once after input validation when at least one valid hotel source starts processing, including runs that later return no saved hotels.

The item event is charged for each hotel result saved to the dataset. Source errors and the run summary are not hotel dataset items. maxItems bounds the number of saved hotel rows.

See the live Pricing tab for current rates and discounts. Review the platform usage and any optional proxy charges shown for your account.

Tips for best results

• Start with a small maximum. Check the fields available for your destination before requesting more hotels.
• Use the right market URL. Locale and page content can affect returned fields.
• Check price coverage. Dates can be supplied, but prices may remain absent from the public response.
• Keep source links. Use sourceUrl and scrapedAt when comparing separate snapshots.

Limits and caveats

The Actor reads the supplied hotel-list pages only. It does not automatically follow pagination, collect room-level offers or guarantee complete destination inventory.

Trip.com content varies by destination, dates and locale. Blocking or changed page structure can prevent extraction. The current implementation fails when no hotels can be extracted from failed sources. Mixed-source runs may retain useful rows and report source errors or pending URLs in RUN_SUMMARY. Inspect that summary before treating a dataset as complete.

Amenities are not extracted by the current implementation. Private accounts, bookings and login-only prices are not supported. This is an independent scraper, not an official Trip.com API.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~trip-com-hotels-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchUrls":[{"url":"https://www.trip.com/hotels/tokyo-hotels-list-228/"}],"maxItems":20}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/trip-com-hotels-scraper').call({
  searchUrls: [{ url: 'https://www.trip.com/hotels/tokyo-hotels-list-228/' }],
  maxItems: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/trip-com-hotels-scraper").call(run_input={
    "searchUrls": [{"url": "https://www.trip.com/hotels/tokyo-hotels-list-228/"}],
    "maxItems": 20,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with Trip.com Hotels Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Trip.com Hotels Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/trip-com-hotels-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Trip.com Hotels Scraper by Fetch Cat, or give it the identifier fetch_cat/trip-com-hotels-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Collect up to 20 hotels from this public Tokyo listing and make a table of their names and available ratings.”
• “Get hotels from these two destination pages and compare the returned guest ratings.”
• “Collect the hotels on this Lisbon listing and prepare a CSV of names, available prices and links.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export Trip.com hotel listings to a spreadsheet?

Yes. Run the Actor with a destination listing URL and export the returned dataset as CSV or Excel. The export contains the hotels found on the supplied pages, not a guarantee of every hotel in the city.

Does this provide Trip.com review text or room availability?

No. It returns listing-level ratings and review counts when available. It does not fetch review text, booking inventory or room details.

Why are prices missing?

The public response may not contain a visible card price. Providing stay dates can change the source response but does not guarantee price coverage. Missing prices remain null.

Why did a run fail or return fewer hotels?

Check that the URLs are supported public hotel listing pages. Read RUN_SUMMARY for source failures and pending pages. Increasing maxItems does not add pagination or make missing source fields available.

Can I use it through an API or an AI assistant?

Yes. Use the API examples or configure Apify's hosted MCP server above. The assistant should use a bounded request and read results from the returned dataset.

Where do I find current charges and alternatives?

Check the Actor's live Pricing tab before running. For other travel sources, see the related Actors below. Their coverage and pricing differ.

Related Actors

• Agoda Hotels Scraper — Hotel listings from another travel source.
• Agoda Reviews Scraper — Collect public Agoda guest-review text, ratings and available traveler metadata.
• Airbnb Listings Scraper — Short-stay listing research.
• Airbnb Reviews Scraper — Reviews for short-stay research.
• Apple Maps Places Scraper — Collect public Apple Maps places with available locations and contact details.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review from the Actor page to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥