Setting/custom booking: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 163: | Line 163: | ||
In this example we will send that a fee applies for pets. Booking.com will not display the amount though. | In this example we will send that a fee applies for pets. Booking.com will not display the amount though. | ||
'''4.1 Future Charges''' | |||
The Booking.com Charges API allows setting date-based fees/taxes using '''FROM''' and '''TO'''. | |||
'''Format:''' | |||
<pre> | |||
FEENAME=amount FROM=YYYY-MM-DD TO=YYYY-MM-DD | |||
</pre> | |||
'''Example:''' | |||
<pre> | |||
AIRPORTSHUTTLEFEE=12 FROM=2026-03-09 TO=2026-05-31 | |||
</pre> | |||
The fee applies only within the defined date range. Outside this period, the previous value applies. | |||
'''Notes:''' | |||
* '''FROM''' is optional (defaults to today) | |||
* '''TO''' is optional (applies indefinitely if not set) | |||
* Both formats are supported: | |||
<pre> | |||
FEENAME 10 | |||
FEENAME=10 | |||
</pre> | |||
'''Unsetting a charge:''' | |||
<pre> | |||
FEENAME=0 FROM=YYYY-MM-DD | |||
</pre> | |||
'''Rules:''' | |||
* Charges cannot overlap | |||
* Avoid using past dates (may cause unexpected results) | |||
* On import, '''FROM''' is only set if it is in the future | |||
'''Booking.com UI behavior:''' | |||
Updating charges may create duplicate entries instead of replacing existing ones. | |||
Recommended flow: | |||
1. Remove existing charges | |||
2. Sync | |||
3. Add new values | |||
4. Sync again | |||
'''5. Security deposit''' | '''5. Security deposit''' | ||