Airbnb Premium Stay Filters API

Provide a destination query and optional language_code to obtain the documented premium-stay catalog. The example response includes status, message and data items with id, title and subtitle describing named tiers. These historical labels are not a promise that the same tiers remain available; inspect the current returned choices before using IDs in properties-search.top_tier_stays. This endpoint was not live-verified. A returned premium category is a search grouping, not an independent quality guarantee, a service entitlement or evidence of special booking access.

API Features

Premium filter ID discovery The documented response maps destination-specific tier IDs to descriptive titles.

Tier subtitles for context The example includes subtitle text that can explain how a returned category is presented.

Historical-label caution Do not hardcode older named tiers as current products without inspecting a fresh response.

Search tier is not a quality warranty A tier choice is filter metadata and does not independently verify quality or arrange services.

Live API Demo

GET /api/project/airbnb-search/get-top-tier-stays-filter

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/get-top-tier-stays-filter?key=<API_KEY>&query=New+York%2C+NY&language_code=en-US'

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/get-top-tier-stays-filter?key=<API_KEY>&query=New+York%2C+NY&language_code=en-US'

📢

Need Help?

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

Use Cases

Populate a premium-stay selector only with choices currently returned for the destination.
Audit an older premium-category integration when historical tier labels disappear or change.
Resolve returned IDs for a query-family top_tier_stays filter without hardcoding names.
Explain a returned premium grouping while separating it from quality guarantees or service entitlements.

Frequently asked questions

Can I assume the named tiers in an older example are still available?

No. The supplied example contains historical tier labels, and this endpoint was not live-verified. Read the current destination catalog and only offer choices actually returned.

Are these IDs the same as stays-search.topTierStays values?

Do not assume so. This catalog belongs to the query-family top_tier_stays input; stays-search separately documents values such as guest_favorite and luxe. Follow the contract of the endpoint being called.

Related operations

Guides

View Subscription Plans →

Read Returned Premium-Stay Filter Choices