# Google Vacation Rentals Scraper (`googleapi/google-vacation-rentals-scraper`) Actor

Extract source-visible Google Travel vacation-rental cards as structured property records with price context, ratings, room details, amenities, nearby-place text, and rendered photos.

- **URL**: https://apify.com/googleapi/google-vacation-rentals-scraper.md
- **Developed by:** [Google API](https://apify.com/googleapi) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

Search public Google Travel vacation-rental results and collect the information displayed on each property card. Records can include property type, capacity, rooms, amenities, price wording, ratings, review counts, and photos.

Optionally enable `includeDetails` to read more information from selected Google property panels, such as descriptions, policies, amenities, nearby transport, and booking offers. Booking and property links are recorded when shown; the Actor does not open those external pages.

### How to use

1. Search one or more destinations with `queries`, or provide Google Travel search URLs in `startUrls`.
2. Set the starting page, page limit, and overall property limit.
3. Optionally enable property details and set the number of detail pages to inspect.
4. Run the Actor and view or export the property records.

Example:

```json
{
  "queries": ["Paris", "Nice"],
  "page": 1,
  "maxPages": 2,
  "maxItems": 30,
  "includeDetails": false
}
```

### Input

| Input | Description | Default |
|---|---|---:|
| `queries` | Cities, regions, landmarks, or other travel destinations. `query` is an alias for one destination. | — |
| `startUrls` | Public Google Travel search URLs. `queries` and URLs can be combined. | — |
| `page` / `maxPages` | Starting result page and maximum pages per destination or URL. | 1 / 3 |
| `maxItems` | Maximum distinct property records across all searches. | 50 |
| `includeDetails` | Read matching public property panels for additional details. | `false` |
| `maxDetailRequests` | Global limit on property detail panels to inspect. | 10 |
| `proxyConfiguration` | Optional proxy configuration for public Google Travel pages. | — |

### Output

Each dataset item represents a vacation-rental property and includes the required `propertyName`. Depending on the card, the record can also contain:

- **Property:** ID, accommodation type, feature summary, guest capacity, bedrooms, bathrooms, and beds.
- **Price and dates:** displayed price text, parsed amount and currency, explicit stay dates, and price basis. A starting or average price is not assumed to be a nightly price.
- **Ratings and amenities:** rating, review count, and visible positive or negative amenity statements.
- **Location context:** searched destination and nearby-place wording when shown. A street address is not inferred from the search destination.
- **Photos and links:** property-card photo URLs, Google Travel listing/details URLs, and any booking or property links shown.
- **Optional property-panel details:** full description, check-in/check-out policies, location disclosure, Google booking offers, health/safety details, and nearby transport when available.

Example dataset item:

```json
{
  "propertyName": "Example city apartment",
  "propertyType": "Apartment",
  "searchLocation": "Paris",
  "priceDisplayText": "Avg €145",
  "startingPrice": 145,
  "currencyCode": "EUR",
  "priceQualifier": "average",
  "priceBasis": "average_displayed",
  "pricePerNight": null,
  "ratingValue": 4.8,
  "ratingScale": 5,
  "reviewCount": 82,
  "guestCapacity": 4,
  "bedroomCount": 1,
  "bathroomCount": 1,
  "bedCount": 2,
  "amenities": ["No crib"],
  "photoUrls": ["https://lh3.googleusercontent.com/example.jpg"],
  "listingUrl": "https://www.google.com/travel/hotels/entity/example-property-id",
  "resultPosition": 1
}
```

Optional fields vary by destination and listing. Google price labels and ratings can change over time. The Output tab shows the available result fields.

### Limits and responsible use

Results depend on Google Travel’s public listings for each destination. More destinations, pages, and optional detail panels increase run time. The Actor does not infer exact street addresses, host contacts, or booking availability from missing information.

Use public listing information responsibly and follow applicable privacy requirements and Google terms. This Actor is not affiliated with Google.

# Actor input Schema

## `query` (type: `string`):

Compatibility alias for a single destination search.

## `queries` (type: `array`):

A city, region, landmark, or other public travel destination. Each location produces Google Travel vacation-rental results.

## `startUrls` (type: `array`):

Optional Google Travel search pages. Only HTTPS Google Travel search URLs are accepted.

## `page` (type: `integer`):

One-based result page to start from for each search. The actor advances through Google Travel's visible results pagination.

## `maxPages` (type: `integer`):

Maximum number of result pages to inspect per destination or supplied start URL. The global maxItems limit can stop earlier.

## `maxItems` (type: `integer`):

Maximum number of distinct vacation-rental properties to save across all searches.

## `requestTimeoutSecs` (type: `integer`):

Maximum navigation and result-loading time for each Google Travel search page.

## `includeDetails` (type: `boolean`):

Read Google Travel property panels for descriptions, policies, amenities, public offers and nearby transport. No booking partner is fetched.

## `maxDetailRequests` (type: `integer`):

Global limit; one Google detail page per property, with a 20-second total deadline.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy configuration passed to the Chromium browser for public Google Travel navigation. It does not bypass access controls.

## Actor input object example

```json
{
  "page": 1,
  "maxPages": 3,
  "maxItems": 50,
  "requestTimeoutSecs": 45,
  "includeDetails": false,
  "maxDetailRequests": 10
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("googleapi/google-vacation-rentals-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("googleapi/google-vacation-rentals-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call googleapi/google-vacation-rentals-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,googleapi/google-vacation-rentals-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7CIOAauAybmrHwc7B/builds/eDJeP8vDg0dpD0Dh1/openapi.json