currencies (B.XML)

This call is intended for the Connectivity Partner to be able to retrieve a list of currency codes with their corresponding currency name that are used on Booking.com. The currency information is based on a subset of ISO 4217 Alphabetic codes and currency names but altered in some cases. The most current list as returned by this call should therefore be considered the authoritative source of currency codes and names for the API.

Step 1: Request for a list of countries and country codes

POST https://supply-xml.booking.com/hotels/xml/currencies

Request — HTTP Message Body Model

<?xml version="1.0" encoding="UTF-8"?>
<request>
  <username>providermachinelogin</username>
  <password>********</password>
</request>

Request — Node Overview

Request — cURL Model

curl -H "Host: providerhostname" \
-H "Connection: keep-alive" \
-H "Content-Length: XXX" \
-H "Cache-Control: no-cache" \
-H "Origin: XXXXXXXXXXXXX" \
-H "User-Agent: Provider User-Agent name" \
-H "Content-Type: text/xml;charset=UTF-8" \
-H "Accept: */*" \
-H "Accept-Encoding: gzip,deflate" \
--http1.1 \
-d @messagebody.xml -X POST \
'https://supply-xml.booking.com/hotels/xml/currencies'

Step 2: Response of currency codes/names

Response — HTTP Message Body Sample

<?xml version="1.0" encoding="UTF-8"?>
<currencies>
   <currency currencycode="EUR" name="Euro" />
   <currency currencycode="USD" name="U.S. dollar" />
   <currency currencycode="BHD" name="Bahrain dinar" />
   <currency currencycode="BWP" name="Botswana pula" />
   <!-- example output. Use the API for a complete updated list -->
</currencies>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXX==] -->

Dual-Currency Countries

Properties located in the following countries have more than one allowed currency. You can use the OTA_HotelDescriptiveContentNotif or Property API to set a different currency for the property when the property status is XML: Being built or Test Hotel. Countries not in the list below support only one allowed currency and is assigned by default.

NOTE: The below values are accurate as of Dec 2024. Expanding the existing currency endpoint to include this information is being considered.