# Hotel Rate Feed for RMS - Verified Google Hotels Quotes (`prixodik/hotel-rate-feed`) Actor

Competitor hotel rates for exact stay dates, guests and currency, with hotel identity confirmation, mismatch rejection, comparability labels and price-change mode for RMS pipelines.

- **URL**: https://apify.com/prixodik/hotel-rate-feed.md
- **Developed by:** [Milchenko Oleksii](https://apify.com/prixodik) (community)
- **Categories:** Travel, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 confirmed hotel quotes

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Hotel Rate Feed for Revenue Management

Get competitor hotel prices for **exact stay dates, nights, guests and currency**. Only hotels that are confirmed to be the ones you asked for produce quotes, and each quote states what is still unknown. The output is built for hotel revenue management systems (RMS), rate-shopping dashboards and pricing analysts.

### What this Actor adds over a raw scraper

Raw hotel-price scrapers return whatever the search engine finds for a name. In our tests the source returned a **different Hilton** for "Hilton Garden Inn Times Square Central". Fewer than a third of quotes named the room, and almost none stated taxes or cancellation terms. This Actor guards against that:

- **Hotel identity check.** A result is confirmed by Google hotel identifier (`googleEntityToken`) or by coordinates within a radius you set. Without either, the Actor checks that every distinguishing word of your hotel name appears in the returned name (a `probable` match). A different hotel is rejected as `mismatch` with the reason and **is not charged**.
- **Comparability labels.** Each quote is `comparable`, `partial` or `not-comparable` and lists `unknownFields` (room name, taxes and fees, cancellation policy, meal plan). A lower price is never presented as a parity violation.
- **Change mode.** With a named state store, `changes` mode returns only new quotes and price moves since the previous run, which suits daily RMS feeds.
- **Match report.** The `SUMMARY` record lists every requested hotel with its match status, returned hotel, offer count and min, median and official price.

### Input

| Field | Description |
|---|---|
| `hotels` | 1–50 hotels: `name`, optional `city`, `googleEntityToken` or `cid`, `latitude` and `longitude` |
| `stays` | 1–10 stays: `nights` (1–14) and either `checkIn` (YYYY-MM-DD) or `checkInDaysAhead` (0–365 days after the run date, UTC) |
| `adults`, `children`, `rooms` | Party size |
| `currency`, `market` | For example `EUR` and `es`, or `USD` and `us` |
| `matchRadiusMeters` | Coordinate tolerance, default 300 m |
| `includeProbable` | Set to `false` to deliver only identifier- or coordinate-confirmed hotels |
| `mode`, `stateStoreId` | `snapshot`, or `changes` with a named store |
| `reportNewQuotes` | In `changes` mode, set to `false` to receive only price moves of quotes already tracked |
| `maxChildChargeUsd` | Spending limit for the underlying price source in this run |

Example:

```json
{
  "hotels": [
    { "name": "H10 Metropolitan", "city": "Barcelona", "latitude": 41.387772, "longitude": 2.167697 },
    { "name": "Catalonia Plaza Catalunya", "city": "Barcelona" }
  ],
  "stays": [{ "checkInDaysAhead": 45, "nights": 2 }],
  "adults": 2,
  "currency": "EUR",
  "market": "es"
}
```

`checkInDaysAhead` is counted from the run date in UTC, so a saved task or schedule keeps asking for future dates. In `changes` mode prices are compared per exact stay date, so when the date moves forward, its quotes are reported as new quotes rather than price moves. Use `checkIn` when you track one fixed date.

### Output

One dataset item per confirmed quote:

- `hotelName`, `matchStatus` (`matched` or `probable`), `matchBasis` (`id`, `geo` or `name`), `matchReason`
- `checkIn`, `checkOut`, `nights`, `adults`, `children`, `rooms`
- `channel` (seller, for example the official site or an OTA), `official`, `roomName`, `totalPrice`, `perNight`, `currency`
- `comparability`, `unknownFields`, `taxesKnown`, `cancellationKnown`
- `change` (`new`, `price-up`, `price-down`), `previousPrice`, `observedAt`, `sourceRunId`

Rejected hotels and hotels without offers appear only in the `SUMMARY` record. They are never charged.

### Pricing

- **$0.005 per delivered confirmed quote**, plus a small start fee.
- Rejected hotels, empty results and unchanged quotes in `changes` mode are not charged.
- **The underlying price source is billed separately.** The Actor runs `factden/google-hotels-scraper` in your account. That actor charges its own published prices: in our tests $0.01–0.03 per stay for three hotels. `maxChildChargeUsd` caps that spend.

### Data source and terms

Prices come from Google Hotels results collected by the third-party Actor `factden/google-hotels-scraper`. This Actor does not contact Google directly. Google's terms restrict automated access. You are responsible for checking that your use of the data complies with the terms that apply to you and to the source. Prices are observations at `observedAt`, not bookable offers, and they may exclude taxes, fees or conditions.

### Limits

- Matching by name alone is `probable`, not proof. Add identifiers or coordinates for confirmed matches.
- Up to 50 hotels × 10 stays per run. One source run is made per stay.
- Room types, meal plans and cancellation terms are often missing in the source and are reported as unknown.

# Actor input Schema

## `hotels` (type: `array`):

1 to 50 hotels. Each needs a name; add city to separate it from the name, and googleEntityToken or latitude/longitude for a confirmed match. Without them, only name-level (probable) matches are possible.

## `stays` (type: `array`):

1 to 10 stays. Each stay has nights (1-14) and either checkIn (YYYY-MM-DD) or checkInDaysAhead (0-365 days after the run date in UTC). Use checkInDaysAhead in saved tasks and schedules so the dates never go stale. One source run is made per stay.

## `adults` (type: `integer`):

Adults per room.

## `children` (type: `integer`):

Children per room.

## `rooms` (type: `integer`):

Number of rooms.

## `currency` (type: `string`):

Three-letter currency code, for example EUR or USD.

## `market` (type: `string`):

Two-letter lowercase country code of the market the source queries from, for example us or es.

## `matchRadiusMeters` (type: `integer`):

Maximum distance between expected and returned hotel coordinates for a confirmed match.

## `includeProbable` (type: `boolean`):

When off, only hotels confirmed by identifier or coordinates produce quotes.

## `mode` (type: `string`):

snapshot returns all quotes; changes returns only new quotes and price moves since the previous run with the same state store.

## `reportNewQuotes` (type: `boolean`):

In changes mode, also return quotes from sellers or rooms not seen before. Turn off to receive only price moves of quotes you already track; new quotes are then recorded silently.

## `stateStoreId` (type: `string`):

Named key-value store that keeps previous prices. Required for changes mode. Letters, digits and hyphens only.

## `maxChildChargeUsd` (type: `number`):

Maximum charge of the underlying price source (factden/google-hotels-scraper) for this run, split across stays. Source runs are billed to your Apify account.

## Actor input object example

```json
{
  "hotels": [
    {
      "name": "H10 Metropolitan",
      "city": "Barcelona",
      "latitude": 41.387772,
      "longitude": 2.167697
    },
    {
      "name": "Catalonia Plaza Catalunya",
      "city": "Barcelona"
    }
  ],
  "stays": [
    {
      "checkInDaysAhead": 45,
      "nights": 2
    }
  ],
  "adults": 2,
  "children": 0,
  "rooms": 1,
  "currency": "USD",
  "market": "us",
  "matchRadiusMeters": 300,
  "includeProbable": true,
  "mode": "snapshot",
  "reportNewQuotes": true,
  "maxChildChargeUsd": 0.5
}
```

# Actor output Schema

## `results` (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 = {
    "hotels": [
        {
            "name": "H10 Metropolitan",
            "city": "Barcelona",
            "latitude": 41.387772,
            "longitude": 2.167697
        },
        {
            "name": "Catalonia Plaza Catalunya",
            "city": "Barcelona"
        }
    ],
    "stays": [
        {
            "checkInDaysAhead": 45,
            "nights": 2
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("prixodik/hotel-rate-feed").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 = {
    "hotels": [
        {
            "name": "H10 Metropolitan",
            "city": "Barcelona",
            "latitude": 41.387772,
            "longitude": 2.167697,
        },
        {
            "name": "Catalonia Plaza Catalunya",
            "city": "Barcelona",
        },
    ],
    "stays": [{
            "checkInDaysAhead": 45,
            "nights": 2,
        }],
}

# Run the Actor and wait for it to finish
run = client.actor("prixodik/hotel-rate-feed").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 '{
  "hotels": [
    {
      "name": "H10 Metropolitan",
      "city": "Barcelona",
      "latitude": 41.387772,
      "longitude": 2.167697
    },
    {
      "name": "Catalonia Plaza Catalunya",
      "city": "Barcelona"
    }
  ],
  "stays": [
    {
      "checkInDaysAhead": 45,
      "nights": 2
    }
  ]
}' |
apify call prixodik/hotel-rate-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,prixodik/hotel-rate-feed"
        }
    }
}
```

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/9y4ScDNVJavVPPcG9/builds/e2HY9gLZvN9pOLD3n/openapi.json