Scrapingdog Weekly Changelog: Oct26-Nov1, 2026

Travel data is one of the most requested categories we hear about, so this week we are happy to ship three new APIs that cover two of the biggest names in the space. On October 29 we added the Tripadvisor Place API, the Booking.com Search API, and the Booking.com Place API. Together they let you go from discovering stays, to inspecting a property, to reading what real travelers think, all from one place.

Each API is available directly through the API and also in the Playground, so you can test requests and inspect responses before writing a single line of integration code.

The Tripadvisor Place API gives you a rich profile of any listed place. Pass in a place ID or a Tripadvisor URL, and you get back the details that matter when you are building a travel experience:

•       Place details such as name, location, and description

•       Ratings and review information

•       Reviews written by travelers

•       Photos

•       Amenities

One detail we are particularly pleased with is regional domain support. Tripadvisor operates different domains for different markets, and you can now choose which regional domain to query. That makes it easier to serve localized content to your users, whether they are browsing from the US, the UK, India, or elsewhere.

Good for: travel guides, destination pages, review aggregation, reputation monitoring for hotels and restaurants, and enriching your own listings with trusted third-party ratings.

The Booking.com Search API is built for discovery. It lets you search Booking.com stays and returns prices, review scores, and availability for the dates you care about. You stay in control of the search through a flexible set of parameters:

•       Stay dates, guests, and rooms, so results reflect a real trip

•       Language and currency, so prices and text match your audience

•       Property and price filters, to narrow results to what a traveler actually wants

•       Pagination, so you can page through large result sets without hitting a wall

Because availability and pricing are included in the results, you can build comparison views, price trackers, or trip planners that show something useful right away rather than a bare list of names.

Good for: hotel comparison tools, travel deal finders, itinerary builders, and market research on accommodation pricing in a destination.

Once a user has found a promising stay, the Booking.com Place API provides the detail view. Using a hotel endpoint, it returns the full picture of a property:

•       Property details

•       Room rates

•       Photos

•       Facilities

•       Review scores

•       Highlights

•       Top matches

Like the search API, it accepts stay dates, guests, rooms, language, and currency, so the rates you retrieve are tailored to the exact trip being planned. The top matches data is a handy way to suggest similar properties without building your own recommendation logic.

Good for: property detail pages, rate monitoring, side-by-side hotel comparisons, and travel apps that need accurate room-level pricing.

The new APIs complement each other nicely. A typical workflow might look like this:

1.      Use the Booking.com Search API to find stays in a city for specific dates and filter by price.

2.      Use the Booking.com Place API to pull room rates, facilities, and photos for the properties a user shortlists.

3.      Use the Tripadvisor Place API to layer in traveler reviews, ratings, and amenities for a second opinion.

The result is a more complete and trustworthy view of a property than either source gives on its own.

If you want to get hands-on quickly, open the Playground and pick any of the three APIs. You can adjust dates, guests, currency, filters, and regional domains, then see exactly what the response looks like. Once you are happy with the shape of the data, move the same request into your own code.

A few tips to get started

•       Start with the Playground. It is the fastest way to understand which parameters change the results.

•       Set currency and language early. Matching them to your audience avoids conversion headaches later.

•       Use pagination deliberately. Fetch only as many pages as your interface actually needs.

•       Pick the right regional domain for Tripadvisor so reviews and details reflect the market you are serving.

Here is a video tutorial about our weekly updates.

This release is part of our ongoing push to broaden coverage across travel and hospitality data. We are keen to hear what you build and what you would like to see next, whether that is more travel sources, additional filters, or deeper detail on existing endpoints. Reach out with your feedback, and keep an eye on next week's update for more additions.

Happy building!