Airbnb Property Detail API - Information by Property ID

Provide the required decimal property id with optional currency and locale. Historical property-search examples identify it at homes[].listing.id; the current live property search instead used demandStayListing identifiers, so do not assume that older extraction path is still present or pass an encoded identifier as a decimal ID. The documented detail response has data of type StayPDPSections, metadata, bookingPrefetchData and seoFeatures with canonicalUrl and descriptive listing text. Undated price-related metadata can be null. This specific detail route was not live-tested; it should not be confused with the verified stays-detail endpoint.

API Features

Query-family property ID input This route uses id, currency and locale rather than listingId, currencyCode and languageCode.

Property metadata enrichment The documented StayPDPSections body carries metadata and descriptive listing information for profile enrichment.

Canonical room-link cross-check Use metadata.seoFeatures.canonicalUrl from the documented shape to verify the source listing identity.

Nullable undated price metadata Do not rely on bookingPrefetchData.price being populated when no dates are requested.

Live API Demo

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

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/properties-detail?key=<API_KEY>&id=<id>&currency=USD&locale=en-US'

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/properties-detail?key=<API_KEY>&id=<id>&currency=USD&locale=en-US'

📢

Need Help?

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

Use Cases

Enrich query-discovered property records with documented profile metadata after resolving the correct decimal ID.
Attach a returned canonical room link to an analyst's property research record for source verification.
Distinguish static property metadata from dated quote observations in an accommodation database.
Audit an older homes[].listing.id integration when current search results use a different identifier structure.

Frequently asked questions

Which ID belongs in properties-detail?

The endpoint expects a decimal property id. Older documented property searches show homes[].listing.id, but the current live homes sample did not. Inspect the actual identifiers and resolve the correct decimal ID instead of forwarding an encoded demandStayListing.id unchanged.

Is this the same verified endpoint as stays-detail?

No. It is a separate query-family route with id, currency and locale. Its documented example is available, but the current live verification covered stays-detail with listingId, not this endpoint.

Related operations

Guides

View Subscription Plans →

Get Property Details for the Query-Based Workflow