Recipes/Competitor Rate Grid
MCP Realtime10 min

Competitor Rate Grid

Rebuild the grid every revenue manager reads each morning — your hotel and its competitor set side by side for a stay — using live Booking.com rates. One call per property, current prices, no scraper.

Competitor Rate Grid

What you'll build

A single self-contained HTML page — no framework, no build step: one row per property, the cheapest available rate for the stay in each cell, your own hotel pinned to the top, and colour coding for where you sit against the set. Room type, board and cancellation come along for free.

Set this up first

Required

The endpoints don't take free text — they take your identifiers. This recipe assumes the things below already exist on your account; while one of them is missing, the call answers with an error or with less than you expect. Each point links to the recipe that walks it.

  1. 01

    Register the hotel in your dashboard

    Veetal resolves the property against Booking.com and assigns it a slug — and that slug, not the hotel name, is what every accommodation endpoint takes.

    Guide: Add your hotel and the comp set you price against →
  2. 02

    Fill in its comp set

    Up to ten competitors on the accommodation detail. Without them this recipe prints your own price list instead of a comparison, and the competitors block comes back empty.

How it works

  1. 01

    Get your API key

    Create your account and copy your key. Start free with 1,000 API credits.

  2. 02

    List your comp set

    List your hotels to get your own slug and its id, then read the competitors configured on that id. Each rival comes back with its Booking.com slug (otas.booking.slug), and that slug is all its live rate call takes: the same call you make for your own hotel.

  3. 03

    One live call per hotel

    Ask Booking.com for the stay, hotel by hotel. Take the cheapest room from each response and you have the grid. Live calls take seconds and consume credits, so keep the set tight.

The call

One call returns every room on sale for that stay, with price per night, board and cancellation. Repeat it for each hotel in your set to fill the grid.

cURL
# 1) Your comp set for this hotel (the id comes from GET /v3/account/accommodation)
curl "https://api.veetal.app/v3/account/accommodation/YOUR_HOTEL_ID/competitors" \
  -H "veetal-api-key: YOUR_API_KEY"

# 2) Live Booking.com rates for your hotel, by its slug
curl "https://api.veetal.app/v3/real-time/accommodation/YOUR_HOTEL_SLUG/rate/booking/2027-03-15/2027-03-16/2" \
  -H "veetal-api-key: YOUR_API_KEY"

# 3) The same for each competitor, with the otas.booking.slug the comp set returned
curl "https://api.veetal.app/v3/real-time/accommodation/COMPETITOR_BOOKING_SLUG/rate/booking/2027-03-15/2027-03-16/2" \
  -H "veetal-api-key: YOUR_API_KEY"

Build it with AI

Connect the MCP →

Paste this prompt into an assistant with the Veetal MCP connected and it builds the whole app against your data — no front-end work.

Prompt
Use my Veetal Connect data to build a competitor rate grid for my hotel,
for a stay I choose, using live Booking.com rates.

I want the view a revenue manager reads every morning: my hotel against the
hotels I compete with, and what each of them is charging right now for that
stay. Work out what data you need and fetch it.

Build it as a single self-contained HTML page — plain HTML and CSS, no
frameworks, no build step, no external requests:

- One row per property: my hotel pinned to the top and visually separated,
  then every competitor.
- For each property, the cheapest available rate for the stay among the rooms
  that fit all the guests, plus the room type, board and whether it is
  refundable. Use the hotel's own Booking.com rates: leave partner offers
  (is_partner_offer, such as Agoda) out of the grid and the ranking, and list
  them apart under the row when one is cheaper.
- Colour each row by where it sits against the set: cheapest, mid, priciest.
- A summary line: the competitors' median rate, my position in the ranking, and the
  gap to the cheapest competitor in money and percent.
- Show how many rooms are left when the data says so — a low count next to a
  high price is a different signal than a high price alone.
- Leave a property visibly empty when it returns no availability, and never
  invent a price.
- These are live calls, so fetch them one hotel at a time and tell me in the
  chat as each one comes back; stamp the page with the time the rates were
  fetched.

Clean and readable at a glance, works in light and dark. Use only real values
from my data.

Questions

Where do the competitors come from?

From the competitor set configured on your account for that hotel. One call returns your rivals, and each one carries its Booking.com slug, which is all its rate call takes.

Why live rates instead of the stored feed?

Because this is the price on Booking.com right now, which is what you act on when you reprice today. The Feed layer is cheaper for reading a whole month of stay dates at once, but it only changes when a scheduled import runs.

How many credits does a grid cost?

One live call per property, at about 1.18 credits each. Your hotel plus five rivals is six calls — around 7 credits — for one stay, and a full set of ten competitors is eleven. A hotel with no availability still counts as a call; a call that fails does not. Keep the set tight and reuse the answer rather than refetching on every page load.

Why does a hotel come back empty?

No availability for that stay, or the stay is below its minimum nights. The recipe leaves the row visibly blank on purpose instead of carrying over an older price.

Build your own

Start free with 1,000 API credits. No credit card, no sales call.

Recipes · MCP

What do you want to build with hotel rates?

Say it in one line and we hand you back the prompt, the recipe if one already exists, and the APIs it runs on — starting with hotel rates.

Try

Browse all recipes →

Whatsapp