Real-time hotel rate monitoring

POST

scrape

curl --request POST \
  --url https://api.scrapeswitch.com/scrape \
  --header 'Authorization: Bearer <token>'

const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.scrapeswitch.com/scrape', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.scrapeswitch.com/scrape"

	req, _ := http.NewRequest("POST", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

Track live room rates across booking sites and hotel pages for rate-parity checks, dynamic pricing, or a travel aggregator — as structured JSON you can poll on a tight interval.

Use case

Rate-parity monitoring: confirm a hotel’s own site matches what OTAs show
Dynamic pricing feeds for a metasearch or booking product
Alerting when a watched property’s rate drops below a threshold

Sample request

Listing pages are almost always JS-rendered and vary rates by selected dates — set js_render, wait for the rate block to load, and use prompt/schema to pull exactly the fields you need instead of parsing HTML yourself.

curl -X POST "https://api.scrapeswitch.com/scrape" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://hotels.example.com/property/123?checkin=2026-10-10&checkout=2026-10-12",
    "js_render": true,
    "wait_selector": "[data-testid=\"room-rate\"]",
    "output": ["json"],
    "prompt": "Extract each room type with its nightly rate, currency, and whether it is sold out.",
    "schema": {
      "rooms": [
        { "room_type": "string", "nightly_rate": "number", "currency": "string", "sold_out": "boolean" }
      ]
    },
    "tag": "hotel-rates.property-123"
  }'

import os
import httpx

response = httpx.post(
    "https://api.scrapeswitch.com/scrape",
    headers={"Authorization": f"Bearer {os.environ['API_KEY']}"},
    json={
        "url": "https://hotels.example.com/property/123?checkin=2026-10-10&checkout=2026-10-12",
        "js_render": True,
        "wait_selector": "[data-testid='room-rate']",
        "output": ["json"],
        "prompt": "Extract each room type with its nightly rate, currency, and whether it is sold out.",
        "schema": {
            "rooms": [
                {"room_type": "string", "nightly_rate": "number", "currency": "string", "sold_out": "boolean"}
            ]
        },
        "tag": "hotel-rates.property-123",
    },
    timeout=60.0,
)
response.raise_for_status()
rooms = response.json()["data"]["json"]["rooms"]
for room in rooms:
    print(room["room_type"], room["nightly_rate"], room["currency"])

const response = await fetch("https://api.scrapeswitch.com/scrape", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    url: "https://hotels.example.com/property/123?checkin=2026-10-10&checkout=2026-10-12",
    js_render: true,
    wait_selector: "[data-testid='room-rate']",
    output: ["json"],
    prompt: "Extract each room type with its nightly rate, currency, and whether it is sold out.",
    schema: {
      rooms: [
        { room_type: "string", nightly_rate: "number", currency: "string", sold_out: "boolean" },
      ],
    },
    tag: "hotel-rates.property-123",
  }),
});

const { data } = await response.json();
data.json.rooms.forEach((r) => console.log(r.room_type, r.nightly_rate, r.currency));

Tracking rates over time

Run the same request on an interval (every 15–30 minutes for fast-moving rates) with the same tag, and log each poll’s rooms array with a timestamp in your own time-series store or database — the API itself doesn’t retain history beyond Request history.

Python

import time

while True:
    rooms = fetch_rates()          # the request above, wrapped in a function
    store_snapshot(property_id, rooms, timestamp=time.time())
    time.sleep(900)  # 15 minutes

Request highlights

Setting	Value	Why
`js_render`	`true`	Rate widgets are almost always rendered client-side
`wait_selector`	the rate block’s selector	Ensures rates have loaded before extraction runs
`schema`	typed `rooms` array	Guarantees a stable shape to store and diff, regardless of page layout
`tag`	per property	Lets you separate cost and history per monitored hotel

Tips

Encode check-in/check-out dates in the url itself — rates are date-dependent, and caching behavior follows the full URL.
Use session_id if the site requires a search to be performed before rates render, so follow-up requests reuse the same session instead of re-searching every time.
Keep polling intervals reasonable — see Scrape best practices on concurrency and session limits before scaling across many properties.

Real-time hotel rate monitoring

curl --request POST \
  --url https://api.scrapeswitch.com/scrape \
  --header 'Authorization: Bearer <token>'

const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.scrapeswitch.com/scrape', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.scrapeswitch.com/scrape"

	req, _ := http.NewRequest("POST", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

Get started

Endpoints

Teams

Billing

Recipes

Monitoring

Real-time hotel rate monitoring

Use case

Sample request

Tracking rates over time

Request highlights

Tips

​Use case

​Sample request

​Tracking rates over time

​Request highlights

​Tips

​Related

Use case

Sample request

Tracking rates over time

Request highlights

Tips

Related