List Locale Identifiers for Query-Based Property Requests
View all Airbnb Search, Prices & Reviews endpoints →This parameter-free endpoint provides the documented locale metadata for the property endpoint family. The example response has status, message and data items with id, language, country and domain. Use returned id values for property locale and catalog language_code inputs. The domain field is the corresponding original Airbnb site domain, not an API base URL. This language catalog was not live-verified and does not describe host-language filter IDs or the separate common-languages languageCode mapping.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/airbnb-search/get-languages No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/get-languages?key=<API_KEY>'
Query Result
Use Cases
- Populate locale choices for query-based property searches and detail requests.
- Apply one returned locale identifier consistently across property filters that use language_code.
- Associate original-listing site metadata with a selected property language variant.
- Avoid mixing host-language filter IDs with property response-localization identifiers in request configuration.
Frequently asked questions
Which returned value belongs in property locale or language_code?
Use the returned id. The documented record also includes language, country and domain, but those labels and domains are not substitutes for the locale identifier.
Should I send API requests to the returned domain?
No. domain is original-site metadata for the corresponding Airbnb locale, not an API base URL or forwarding configuration. Continue using the configured public endpoint and its documented parameters.