List currency codes and labels for travel search forms
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Retrieve currency reference data with a GET request and no declared input parameters. The truncated, unverified source response example shows a data object with majorCurrencies and minorCurrencies arrays; example entries contain code, name, and symbol strings. These are documented sample fields, not operation-specific probe observations, because no saved probe call is available for this endpoint. Use the codes actually returned to populate a travel-form currency selector, retaining the code separately from the display name and symbol. The multi-city flight operation documents this list as a source for its currencyCode input. If another travel operation names its currency input differently, map it explicitly in the client rather than assuming identical parameter names. This endpoint documents currency metadata, not exchange rates, converted totals, or guaranteed currency acceptance by every travel search.
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/tripadvisor-data/get-currency No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-currency?key=<API_KEY>'
Query Result
Use Cases
- Populate a travel-form currency dropdown from codes and names actually returned by the currency endpoint.
- Prepare a shared client-side currency preference model while mapping each travel operation to its own documented parameter name.
- Display a readable currency name and symbol beside a saved currency code without presenting the list as a conversion service.
- Evaluate grouped currency-picker layouts using the example majorCurrencies and minorCurrencies lists, reconciling any repeated codes in client display logic.
Frequently asked questions
Does Get Currency require a location or any other parameters?
No. This GET operation declares no input parameters. Destination searches, travel dates, and a base currency are not part of its documented request.
What response fields are documented for currency entries?
The truncated source example shows data.majorCurrencies and data.minorCurrencies arrays with code, name, and symbol string fields. No operation-specific probe is saved, so verify the actual response before depending on this sample structure.
Can these codes be used in a multi-city flight search?
The multi-city flight currencyCode documentation explicitly points to Get Currency. Use a code actually returned by the list. For any other operation, check its own parameter name and supported behavior instead of assuming the same input contract.
Does the endpoint return exchange rates or convert fares?
No exchange-rate or conversion fields are documented. The example contains currency identifiers and display metadata, not a rate table or converted travel prices.
Should majorCurrencies and minorCurrencies be treated as disjoint lists?
Do not assume that. The unverified example repeats some codes across the two arrays and does not define a classification rule. A combined selector can reconcile repeated codes while retaining the grouping information it needs.