# Hotel Reviews Radar (`titan_coder/hotel-reviews-radar`) Actor

Daily radar of NEW hotel reviews on Agoda, deduplicated across runs. Pay only for genuinely new, dated reviews you have not seen before; baseline, errors and repeats are free.

- **URL**: https://apify.com/titan\_coder/hotel-reviews-radar.md
- **Developed by:** [Radu Furtuna](https://apify.com/titan_coder) (community)
- **Categories:** Travel
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 new review delivereds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Hotel Reviews Radar 🛎️

**Only the reviews you haven't seen yet — never the ones you already have.**

Most review scrapers hand you the entire history every single run, and you pay for the same 500 old reviews again and again. This one remembers what it already showed you. Run it daily and you get exactly what's new since yesterday — nothing else.

### Why hotels and management companies use this

- **Never miss a new review again.** Point it at your hotels on Agoda; every run finds what's genuinely new since the last check, so a fresh 1-star review doesn't sit unanswered for a week.
- **Pay only for what's actually new.** The first run establishes a baseline of your current reviews — completely free. From then on, you're billed once per new review, ever, no matter how many times you re-run.
- **No duplicate charges, guaranteed.** Every review is tracked with a permanent, durable record — a re-run, a retry, or a crash never bills you twice for the same review.
- **Built for daily automation.** Attach an Apify Schedule and forget it — a clean digest lands in your dataset (and optionally your webhook) every morning.

### How it works

1. Give it your hotel pages on Agoda and a `monitorId` to name this watch.
2. The first run silently catalogs every review currently visible — free, no charge, no data written yet.
3. Every run after that fetches the latest reviews and delivers only the ones with a real, dated publish time after your monitor started — with the author, rating, text, and date.
4. A short digest tells you what's new across all your hotels; an optional webhook can push it to Slack, Telegram, or your own system (via Make/Zapier/n8n).

### What you pay for

**One event only — `review-delivered`.** Billed once per genuinely new review: real Agoda-sourced content, a reliable publish date after your monitor's baseline. Your very first run's entire visible history is free. Repeat deliveries of a review you've already been billed for — impossible, by design (a permanent record per review prevents it). Errors, blocked attempts, and unreadable data cost nothing.

On the rare occasion the charge itself can't be confirmed after a review has already been written to your dataset, we never retry it and never bill you for it later — you keep that row for free rather than risk a duplicate charge. This is intentional: the system always favors undercharging over overcharging.

### What it does NOT promise

Real-time push notifications the moment a review appears (this is a scheduled daily check, not a live feed from Agoda), sentiment analysis or an AI-drafted reply, tracking of edited or disappeared reviews (v1 only delivers new reviews — it does not report when a previously-seen review is removed or changed), or coverage of Booking.com/TripAdvisor/Expedia (v1 covers Agoda only).

### Input

| Field | What it does |
|---|---|
| `monitorId` | Names this watch's own durable history — required, since the whole point is remembering what you've already seen |
| `hotels` (1–30) | Agoda hotel page URLs |
| `notifyOn` | `new_reviews` (default) fires the webhook only when something new showed up; `always`/`never` for the rest |
| `webhookUrl` | HTTPS only; delivers the daily digest of new reviews as JSON |

### Output

- **Dataset** — one row per genuinely new review found: reviewer, rating, title, text, publish date, and when this monitor first saw it. In the vast majority of cases this is also the review you were billed for; in the rare edge case above, it's a row you got for free.
- **Key-value store** — a short digest (per-hotel counts, average rating, negatives flagged) and a coverage report showing how many hotels answered cleanly vs. partially vs. failed, with reasons. The digest and any webhook notification only ever count reviews you were actually billed for.
- **Run status** — a clear reason on bad input, a busy monitor, low coverage, or a run that overran its time budget (reported as failed rather than a silently truncated "success"); anything already saved and billed stays saved and billed.

### Limits (v1)

Up to 30 hotels, up to 8 pages of reviews per hotel per run (Agoda-only in v1 — Booking.com, TripAdvisor, and Expedia are on the roadmap); one retry per hotel on a transient error; an early stop if too many hotels fail in a row, so a bad run doesn't burn through your budget for nothing.

### A note on the source

Data comes from Agoda's public review pages via the same request pattern a browser makes. Agoda's Terms of Service restrict automated access — use this at your own discretion.

# Actor input Schema

## `monitorId` (type: `string`):

Name of this monitoring set (a-z, 0-9, dash; up to 40 chars). Keeps its own durable history of already-seen reviews — required, since the whole product is about dedup between runs.

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

1-30 Agoda hotel page URLs (https://www.agoda.com/<slug>/hotel/<city>.html). Only Agoda is supported in v1.

## `sources` (type: `array`):

v1 supports only "agoda". Kept as a list for schema compatibility with future sources.

## `language` (type: `string`):

Optional. Reviews are not filtered by language unless set.

## `notifyOn` (type: `string`):

new\_reviews — post the webhook only when new reviews were found; always — post it every run; never — do not call webhookUrl at all.

## `webhookUrl` (type: `string`):

Optional. Receives the daily digest of new reviews as JSON (POST). HTTPS only; private/loopback addresses are rejected; redirects are not followed.

## Actor input object example

```json
{
  "monitorId": "my-hotels",
  "sources": [
    "agoda"
  ],
  "notifyOn": "new_reviews"
}
```

# Actor output Schema

# 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 = {
    "monitorId": "my-hotels",
    "sources": [
        "agoda"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("titan_coder/hotel-reviews-radar").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 = {
    "monitorId": "my-hotels",
    "sources": ["agoda"],
}

# Run the Actor and wait for it to finish
run = client.actor("titan_coder/hotel-reviews-radar").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 '{
  "monitorId": "my-hotels",
  "sources": [
    "agoda"
  ]
}' |
apify call titan_coder/hotel-reviews-radar --silent --output-dataset

```

## MCP server setup

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

```

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/e80Mbi1MklGZidCgp/builds/AqmLbwtHXf552vJUm/openapi.json