Airbnb Stay Details API - Listing Profiles and Amenities

Pass a listingId obtained from stays-search; optional checkinDate, checkoutDate, guest counts, currencyCode and languageCode provide trip context. The live response returned status:true, message:Successful and data of type StayPDPSections with sectionContainer, metadata and other section collections. sectionContainer entries identified their sections and contained title, description, amenities, location and reviews. Metadata matched the selected Paris listing, capacity and original room link. Parse sections by their identifiers rather than assuming a flat property object or fixed section order; an undated detail response is not a dated price quote.

API Features

Matched stay-profile identity Live detail metadata matched the listing selected from the stay-search response.

Section-container profile content Find title, description, amenity, location and review sections without flattening away their section types.

Capacity and original room context Use returned metadata and sharing information to cross-check the public listing and stated guest capacity.

Optional detail trip context Request the profile with dates and guest composition when a selected stay needs contextual information.

Live API Demo

GET /api/project/airbnb-search/stays-detail

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/stays-detail?key=<API_KEY>&listingId=1173047051903832695&adults=2&currencyCode=USD&languageCode=en-US'

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/stays-detail?key=<API_KEY>&listingId=1173047051903832695&adults=2&currencyCode=USD&languageCode=en-US'

📢

Need Help?

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

Use Cases

Build a read-only stay profile with descriptions and amenity sections after a traveler selects a search card.
Enrich an internal accommodation shortlist with capacity and location context from matched listing metadata.
Cross-check a search-to-detail join against the returned original room link before storing the profile.
Extract traveler-relevant sections without depending on their position in a large nested detail response.

Frequently asked questions

Is the stay detail body a flat listing object?

No. The observed data used StayPDPSections with sectionContainer entries, each carrying a section identifier and nested section content. Locate the relevant section rather than relying on an array index or assuming title is at data.title.

Does an undated stay profile provide my trip's final price?

No. Detail can be requested without dates, but a trip-specific comparison should use stays-price-detail with the listing ID, future check-in/check-out dates, guests and currency held consistent.

Related operations

Guides

View Subscription Plans →

Get Airbnb Stay Details by Listing ID