Airbnb Property Search API - Cities and Guests

Find properties with a destination query such as Paris, France. Optional checkin and checkout dates use YYYY-MM-DD; adults, currency, locale, page, budget and returned filter IDs refine the request. The observed positive body had status:true, a Paris-specific message, currentPage, resultsPerPage, totalPages, totalResultCount and data with filters and a nonempty homes array. Live homes included title, nameLocalized, photos, demandStayListing identifiers and coordinates, and structuredDisplayPrice. This shape differs from stays-search: the current sample did not expose homes[].listing.id. An impossible destination returned HTTP 200 with status:false, message Query is not available, zero counts and data:null. Treat that as a failed query, not a measured empty market.

API Features

Destination-text property discovery Start from a human-readable city or destination rather than a prior place-ID lookup.

Homes-specific response parsing Read the observed data.homes collection instead of assuming the separate searchResults schema.

Property filter catalog in context Use destination-specific filter IDs for amenities, privacy type, host language and other supported selections.

Explicit unavailable-query detection Distinguish status:false and data:null from a successful property response using the business message and counts.

Live API Demo

GET /api/project/airbnb-search/properties-search

Query *

Checkin (optional)

Checkout (optional)

Adults (optional)

Children (optional)

Infants (optional)

Pets (optional)

Currency (optional)

Locale (optional)

Page (optional)

Accessibilities (optional)

Amenities (optional)

Category (optional)

Has allows pets (optional)

Has instant book (optional)

Has superhost (optional)

Host language (optional)

Max price (optional)

Min bathroom (optional)

Min bed (optional)

Min bedroom (optional)

Min price (optional)

Property type (optional)

Self check in (optional)

Top tier stays (optional)

Type of place (optional)

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/properties-search?key=<API_KEY>&query=Paris%2C+France&adults=2&currency=USD&locale=en-US&page=1'

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/properties-search?key=<API_KEY>&query=Paris%2C+France&adults=2&currency=USD&locale=en-US&page=1'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Create a city-based rental shortlist filtered by trip dates, guest counts, budget and room privacy.
Record timestamped advertised-rate observations for a local comparable-property sample without implying historical coverage.
Let travelers refine a text destination with pet-friendly, self-check-in and instant-book flags without making a reservation.
Flag unresolvable destination queries in a research pipeline instead of recording zero listings for that market.

Frequently asked questions

Does HTTP 200 mean the destination search succeeded?

Not necessarily. The observed nonexistent destination returned HTTP 200 with status:false, data:null, Query is not available and zero result counts. Check the business status before processing homes or interpreting counts.

Can I assume every home contains listing.id?

No. Older documented examples refer to homes[].listing.id, while the current live homes used demandStayListing.id and had no listing object. Inspect the actual response and do not pass an encoded demandStayListing identifier as a decimal property ID without resolving the correct ID.

Related operations

Guides

View Subscription Plans →

Search Airbnb Properties by City or Destination