Read the sold-out signals before your comp set does
Your PMS knows your pace. It knows nothing about the market's. By the time a spike shows up in your own bookings the rest of the city has already repriced, and the nights you sold cheap were the ones everyone else sold out of. Availability across the market is the earliest signal there is.

What you'll build
A demand calendar built from what is left on sale rather than from what you have sold: which nights the market is closing out, where the spikes are forming, which dates have blackout patterns, and the nights the market is closing while your own hotel is still on sale.
Set this up first
RequiredThe 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.
- 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 → - 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
- 01
Decide the window that matters
Pace signals are useless at ninety days and gold at fourteen. Pick the window where you still have levers and stop scanning beyond it.
- 02
Read the market, then read yourself
Market availability first, your own hotel second. The interesting number is the gap: nights where your comp set is closing and you are still on sale.
- 03
Watch the disappearances
The signal is not what is on sale, it is what is no longer on sale. A competitor closing one date is worth more than any rate it published.
The call
Availability for a date range tells you what is still on sale. What is missing from the answer is the part worth reading.
curl "https://api.veetal.app/v3/real-time/accommodation/YOUR_SLUG/availability/booking/2027-03-01/2027-03-30/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.
Using my Veetal Connect data, find the demand signals in the next 30 nights for my
market.
Check live availability on Booking.com, night by night, for my hotel and every hotel
in its comp set, and tell me:
- which nights are closing out — competitors with no availability left for that night
- whether that is one hotel (noise) or several (signal)
- where the closures cluster, and whether an event in my city explains them (if my
city is set up as a location on my account)
- any blackout pattern: dates nobody is selling, which usually means something
structural rather than demand
- the nights the market is closing while my own hotel is still on sale — that is
where the gap is widest
Each hotel is one live request that costs credits, so tell me how many calls you will
make before you run them. Days Booking.com could not read come back as errors, not as
sold out: leave them out instead of counting them.
Rank the nights by how much I should care, and for the top three tell me what you would
do tonight. Be explicit about which signals are strong and which are one hotel away
from being nothing.Questions
Does this need my PMS connected?
No. Everything comes from live availability on Booking.com, for your hotel and for its comp set, once both are registered on your account. Your own hotel's availability is the other side of the comparison: a night you are still selling while the market closes is the decision about your inventory.
How early is early?
Earlier than your own booking curve, which is the point. A market closing out for a date you still have wide open is a warning you get days before the reservations would have told you.
Is an unavailable night really a sold-out?
Usually, not always — a hotel can close the night on Booking.com and keep selling it elsewhere. Days Booking.com could not read come back as errors, not as unavailable. Treat one closure as noise and a pattern across several hotels as a signal.
Can it explain a spike?
Cross it with the events of your city, if you have it registered as a location. A cluster of sold-out nights with a congress underneath it prices differently from the same cluster with no explanation — one repeats next year, the other might not.
What does it cost?
Each hotel is one live request of 5 credits, whatever the window up to a year: your hotel plus a full comp set of ten is 55 credits a pass. Errors are not charged, and a repeat of the same request inside the cache window costs nothing.
Build your own
Start free with 1,000 API credits. No credit card, no sales call.
What do you want to build with availability?
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 availability.