Skip to content
Happy Endpoint
airbnb vrbo vacation-rentals short-term-rental travel-data

No public Airbnb API: short-term rental data in 2026

Airbnb has no self-serve API and applications are closed. What vacation rental data you can still get, and how Vrbo rates and availability fill the gap.

Happy Endpoint

Happy Endpoint Team

2 min read
No public Airbnb API: short-term rental data in 2026

Search for “Airbnb API” and you will find a developer portal, partner documentation, and a lot of blog posts explaining how to apply. What you will not find is a way to actually get a key.

Airbnb has no public API. Access is limited to approved enterprise partners, mostly vetted property management systems, and the partner programme is effectively closed to unsolicited applicants. Airbnb approaches partners directly rather than the other way round. If you are building short-term rental analytics, a travel metasearch product, or a revenue tool, you are not getting in through the front door.

So the practical question is not “how do I get the Airbnb API” but “what rental data can I actually get, and is it good enough”.

What short-term rental data is used for

Four jobs dominate:

Rate benchmarking. What are comparable properties charging on these dates, in this neighbourhood, at this bedroom count. Hosts and property managers use it to price; investors use it to underwrite.

Occupancy and availability analysis. Which nights are booked across a market, how far ahead, and how that moves through the season. Availability calendars are the raw material for every occupancy estimate.

Supply and competitor tracking. How many listings exist in a market, who runs them, how professionalised the market is, and how that changes.

Guest sentiment. What reviewers consistently praise or complain about, which feeds both product decisions and listing optimisation.

Every one of these needs the same underlying fields: nightly rates over a date range, a day-by-day availability calendar, property attributes, and reviews. None of them strictly require Airbnb specifically. They require a representative sample of the short-term rental market.

Why Vrbo is a reasonable proxy

Vrbo is one of the largest vacation rental marketplaces in the world and is owned by Expedia Group. Its inventory skews toward whole homes, which is exactly the segment most investor and revenue analysis cares about. In many leisure and coastal markets in the US and Europe, the overlap with Airbnb’s whole-home inventory is substantial, and a meaningful share of properties are listed on both.

That last point matters more than it sounds. In markets with heavy cross-listing, Vrbo pricing and availability track the same underlying calendar the host is managing across channels. You are not looking at a different market; you are looking at the same properties through a different window.

Where it is weaker: Vrbo has proportionally less private-room and urban-apartment inventory than Airbnb. If your product is specifically about shared rooms or dense city stays, treat Vrbo as partial coverage rather than a substitute.

What the Vrbo API gives you

The Vrbo API covers 21 endpoints. The ones that matter for analytics:

Search, four ways. By destination region, around a coordinate, inside a rectangular map bounding box, or from a pasted Vrbo search URL. All accept check-in and check-out dates, guest and pet counts, price ranges, bedroom and bathroom minimums, property types, and amenity filters. /locations-autocomplete turns a place name into the region ID the search endpoints need, and /neighborhoods narrows to named areas within a destination.

Rates for a real stay. /property-prices returns bookable rate plans and the total for specific dates, not an indicative nightly figure. This distinction is the difference between a usable benchmark and a misleading one, because short-term rental pricing depends on length of stay, day of week, season, and per-property minimum-stay rules.

A day-by-day calendar. /property-availability returns availability and nightly price per date. This is the endpoint occupancy models are built on.

Cancellation terms. /property-cancellation-policy returns the actual refund schedule for the dates you queried, which materially affects how comparable two listings are.

Property depth. Full detail by ID or URL, the complete amenities list, a room-by-room breakdown of beds and bathrooms, the full photo gallery grouped by room, house rules and check-in times, and location with nearby points of interest and drive times.

Reviews and hosts. Paginated guest reviews, plus /property-reviews-summary, which returns a scorecard alongside an AI digest of what guests repeatedly mention. /property-host returns the host profile including Premier Host status and response scores, and /host-listings returns their other properties in the destination, which is how you separate individual hosts from professional operators.

A worked example: benchmarking a market

Say you want median nightly rate for three-bedroom homes in a coastal market over a summer weekend.

  1. /locations-autocomplete with the destination name to get the region ID.
  2. /search with that region, your dates, bedrooms=3, paging through results.
  3. /property-prices per property for the exact dates, which gives the real bookable total rather than a headline rate.
  4. Optionally /property-availability across a wider window to see how much of the season is already booked.

The reason step 3 exists as a separate call is the reason most rate benchmarks are wrong: the number shown in search results is not the number a guest pays. Fees, length-of-stay discounts, and minimum-stay rules move it.

What you cannot get from any of this

Be clear about the limits, because they matter for what you can honestly claim.

Bookings. No public rental API lets you create a reservation on Airbnb or Vrbo. This is listing and pricing data, not a booking channel.

Confirmed occupancy. An unavailable night is not necessarily a booked night. Hosts block dates for personal use, maintenance, and minimum-stay mechanics. Every occupancy figure derived from calendar scraping, including from the well-known analytics vendors, is an estimate. Say so in your product.

Host identity or contact details. Public profile information only.

Historical rates you did not collect. These APIs return the current state. If you want a time series, you have to sample on a schedule and store it yourself. Start collecting earlier than you think you need to.

Where this leaves you

If you need Airbnb specifically and you are a property management system, apply to the partner programme and wait. For everyone else, the realistic path to short-term rental data is portal data, and the analysis you can do with a complete Vrbo picture, real bookable rates, and full availability calendars covers most of what teams actually build.

The Vrbo API is on RapidAPI with a free tier. For hotel rates, flights and car rentals alongside it, see the Priceline Pro API, or browse the Travel Data hub.

Disclaimer

Happy Endpoint is not affiliated with, endorsed by, or sponsored by Airbnb, Vrbo, or Expedia Group. All data is collected from publicly available sources. Third-party access terms are as we understood them at the time of writing and change without notice.

Back to Blog
Share:

Follow along

Stay in the loop - new articles, thoughts, and updates.