Booking List Supported Travel Currencies API

Inspect documented supported currency values, optionally filtering with name. Other currency-aware endpoints reference the returned code value for currency_code or baseCurrency. This reference response was not live-validated, so inspect actual code/name fields and filter behavior before building a selector. This is a supported-currency lookup, not an exchange-rate or guaranteed conversion endpoint.

API Features

Supported-currency reference request Inspect currency choices before submitting currency-aware travel requests.

Optional currency name narrowing Evaluate the name parameter rather than assuming a fixed local currency list.

Documented code reuse Retain supported code values for the relevant currency input.

Currency list distinct from conversion Do not interpret a supported code as a live exchange rate.

Live API Demo

GET /api/project/booking/currencies

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/currencies?key=<API_KEY>'

curl -X GET 'https://api.opendata-api.com/api/project/booking/currencies?key=<API_KEY>'

📢

Need Help?

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

Use Cases

Evaluate a supported-currency selector for an accommodation comparison tool.
Validate a traveler's requested reporting currency before hotel detail retrieval.
Audit currency-code choices in saved price-snapshot configurations.
Separate currency support metadata from a trip-cost conversion worksheet.

Frequently asked questions

Does this return exchange rates?

It is documented as a supported-currency lookup. Use exchange-rates for the separate reference conversion workflow, whose live response also needs validation.

Should I use a currency name or code in hotel requests?

Documentation points to the returned code value for currency_code. Inspect actual supported entries because this reference route was not live-validated.

Related operations

Guides

View Subscription Plans →