Airbnb Property Autocomplete API - City Search Suggestions

Provide the required query, currency and locale to suggest location text for the query-based property workflow. Use currency identifiers from get-currency and locale identifiers from get-languages. The documented response has status, message and data containing country_code and display_name suggestions, such as city labels for stays or experiences. Unlike common-auto-complete, this example does not expose the reusable placeId required by stays-search and experiences-search. This text-suggestion endpoint was not included in the live verification set.

API Features

Text-query suggestion entry point Resolve partial destination text into display_name choices for the property-search query field.

Country-code suggestion labels The documented data items include country_code for disambiguating similarly named destinations.

Property locale and currency inputs This autocomplete requires locale and currency, matching the query-based property endpoint family.

Separate from place-ID autocomplete Keep this compact display-name response distinct from the richer common destination picker.

Live API Demo

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

API Response (JSON)

{}

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

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

📢

Need Help?

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

Use Cases

Offer city-name suggestions in a property-search form that ultimately sends query text.
Display country context beside ambiguous query-based destination suggestions.
Refresh text suggestions when the user changes the property form's locale setting.
Route destination selections into a text-search interface without expecting an encoded place identifier.

Frequently asked questions

Can this response supply the placeId for stays-search?

The documented text-autocomplete example only includes display_name and country_code. Use common-auto-complete when you need explore_search_params.place_id for the stay or experience endpoint family.

Why are currency and locale required for this autocomplete?

They are required inputs of this endpoint contract. Supply a currency identifier from get-currency and a locale identifier from get-languages along with the partial query; they use different names from currencyCode and languageCode.

Related operations

Guides

View Subscription Plans →

Suggest Destination Text for Property Searches