MindCase
Kritish Puri

Airbnb and Booking.com Data for Market Research

Evaluating a market for short-term rentals means reading both platforms at once — what's already listed on Airbnb, and what it's competing against on Booking.com.

airbnbbooking
Airbnb and Booking.com Data for Market Research

Say you're deciding whether a two-bedroom apartment in Lisbon's Alfama district is worth buying as a short-term rental. The question isn't just "what do similar Airbnbs charge" — it's whether the market can actually support another listing, and what it's up against. Alfama's existing Airbnb supply tells you the first half. The hotels a guest would book instead, if your listing didn't exist, tell you the second.

Most market research stops at one platform. Pull only Airbnb data and you'll price against other hosts correctly, but miss the ceiling a cluster of cheap hotels two streets over sets on the whole neighborhood. Pull only hotel data and you'll never see the fragmented, apartment-shaped demand that made someone list on Airbnb in the first place. The answer to "is this a good market" lives in the gap between the two, not in either one read alone.

If you're an agent (or building one) reading this rather than a human, the full machine-readable schema for every endpoint below lives at mindcase.co/skills.md.

What does evaluating a market for short-term rentals actually take?

Three questions, in order:

  • What's already listed, and at what price? Not the headline rate on one popular listing — the distribution across every comparable property in the neighborhood, for the actual dates you're pricing against.
  • What do guests say once they've stayed? A listing charging near the top of the range with a thin review history is a different risk than one charging the same with 400 reviews and a consistent rating.
  • What's the next-best alternative for a guest who skips Airbnb entirely? A 3-star budget hotel two blocks away sets a real price ceiling that an Airbnb-only view never shows you.

Airbnb's own listing search caps out at roughly 300 results per query and 1,000 total for a given area — workable for browsing, not for building a full inventory view of a neighborhood. That's the gap a direct pull closes.

Why look at both Airbnb and Booking.com instead of just one?

Because they're not really the same market. Airbnb supply is what you're about to compete with directly — other hosts, other listings, the same booking flow a guest would use to find your unit. Booking.com supply is what a guest picks when they decide a hotel room beats an apartment: a front desk, no cleaning fee negotiation, points programs some travelers won't give up.

A neighborhood with heavy Airbnb saturation but weak, expensive hotel options still has room for a well-run listing — guests priced out of hotels have nowhere else to go. The reverse is also true: a neighborhood that looks under-supplied on Airbnb but sits next to a strip of 2-star hotels charging $60 a night has a price ceiling no listing description fixes. Reading one platform alone hides which case you're actually in.

Guest reviews sharpen that read further. A hotel's disliked field naming the same complaint across dozens of reviews — no elevator, thin walls, a front desk that closes at 10pm — is a gap a well-run apartment listing can close outright. An Airbnb listing's review history showing consistent 5-star ratings at a price above the neighborhood median is evidence the market will actually bear that rate, not just that one host is hoping it will.

How do you pull the full picture for one neighborhood?

Four calls cover it: current Airbnb supply, what past guests said about it, the competing hotel inventory, and what those guests said too.

How do you get every active Airbnb listing in the area?

curl -X POST "https://api.mindcase.co/v1/data/airbnb/listings/run?wait=true" \
-H "Authorization: Bearer $MINDCASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "params": {
    "location": "Alfama, Lisbon, Portugal",
    "checkIn": "2026-11-10",
    "checkOut": "2026-11-14",
    "adults": 2,
    "minBedrooms": 2,
    "currency": "USD",
    "maxResults": 0
  }
}'

# $0.002 per listing

Airbnb Listings API takes a location string instead of a list of URLs when you don't already have specific listings in mind, and returns 27 fields per property — pricePerNight, totalPrice, available, ratings, amenities, host, and the raw listingUrl you'll need for the next step. Setting checkIn/checkOut matters here: without them, price and availability fields come back empty, and a neighborhood supply count without prices isn't a market view, just a list. maxResults: 0 pulls everything matching the filters instead of stopping at a default sample.

How do you check what guests say about specific listings?

curl -X POST "https://api.mindcase.co/v1/data/airbnb/reviews/run?wait=true" \
-H "Authorization: Bearer $MINDCASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "params": {
    "urls": "https://www.airbnb.com/rooms/12345678",
    "maxResults": 0
  }
}'

# $0.002 per review

Airbnb Reviews API takes one listingUrl at a time from the previous step's results, and returns 19 fields — reviewText, rating, postedDate, and hostResponse, among others. Run it against the handful of listings closest to your target price and bedroom count, not the full neighborhood set: a listing charging near the top of the range with 400 consistent reviews is carrying real pricing power: one charging the same with six reviews is closer to a coin flip.

How do you see what hotels are charging for the same dates?

curl -X POST "https://api.mindcase.co/v1/data/booking/listings/run?wait=true" \
-H "Authorization: Bearer $MINDCASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "params": {
    "location": "Alfama, Lisbon, Portugal",
    "checkIn": "2026-11-10",
    "checkOut": "2026-11-14",
    "propertyType": "Hotels",
    "currency": "USD",
    "maxResults": 0
  }
}'

# $0.002 per listing

Booking Listings API mirrors the Airbnb call: location for an area search, checkIn/checkOut required for price and room data to populate at all, propertyType to filter out hostels and guesthouses if you only want direct hotel competition. It returns 32 fields, including guestScore, priceFrom, starRating, and facilities — set starsCountFilter or minScore if you want to isolate the budget tier specifically, since that's the segment closest to what a mid-market Airbnb listing actually competes against.

How do you read guest sentiment on those hotels?

curl -X POST "https://api.mindcase.co/v1/data/booking/reviews/run?wait=true" \
-H "Authorization: Bearer $MINDCASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "params": {
    "urls": "https://www.booking.com/hotel/pt/example-alfama.html",
    "maxReviewsPerHotel": 0,
    "sortBy": "f_recent_desc"
  }
}'

# $0.002 per review

Booking Reviews API takes one hotel URL per call and returns 18 fields — liked, disliked, rating, travelerType, and room, split out separately rather than folded into one text blob. Run it across the 3-4 hotels closest to your target price band: the recurring complaint isn't found in any single review, it's the pattern across a hotel's full review history that the disliked field makes easy to spot.

What can't you get from Mindcase?

Two cases.

Historical price trends aren't stored anywhere. Every call above returns what's listed and priced right now. A read on how Alfama's Airbnb rates moved over the last two tourist seasons means running the same airbnb/listings call on a schedule and building that history yourself — there's no backdated pricing endpoint to query instead.

Occupancy rate isn't a field either platform publishes. available on an Airbnb listing tells you whether it's bookable for the exact dates you searched, not what fraction of the calendar year it stays booked. Estimating occupancy from public data means inferring it from review frequency and posted-date gaps over time, not reading it off a single call.

Which endpoint should you use for which job?

EndpointInputPriceBest for
Airbnb ListingsLocation or listing URLs$0.002 / listingMapping Airbnb supply and pricing for a neighborhood
Airbnb ReviewsOne listing URL$0.002 / reviewReading guest sentiment on specific comparable listings
Booking ListingsLocation or hotel URLs$0.002 / listingMapping the hotel alternative a guest would book instead
Booking ReviewsOne hotel URL$0.002 / reviewFinding the specific complaints a listing can position against

FAQ

No. Both endpoints read public listing and review data with no login, host account, or booking required.

Price, availability, and room fields come back empty on both airbnb/listings and booking/listings. Location and property details still populate, but the market read is incomplete without dates.

No. Both airbnb/reviews and booking/reviews take one URL per call, so comparing five listings means five separate calls, one per property.

It scales with what you request. 40 Airbnb listings plus 150 reviews across 3 of them runs about $0.38 ($0.08 for listings, $0.30 for reviews); the same shape on Booking.com costs the same.

It returns every listing matching your filters, not a fixed sample — set to 0 on both airbnb/listings and booking/listings when you want the full set instead of a capped count.