Overview
This section describes the procedure for creating a channel from the [Admin Console] → [Channel] → [Add channel] button.
Here are the specifications and notes regarding synchronization with Expedia.
Details
Advance preparations for connecting with Expedia
*Advance Preparation
Before creating the Expedia Channel on AirHost, please complete your property connection settings on the Expedia Group website.
On the Expedia management page, Rooms and Rates → Connectivity settings, select "AirHost" as the system supplier and then "Confirm".
After our system automatically approves, you will receive an email from Expedia confirming the completion of the process.
You can then create the corresponding new channel in the AirHost management screen. (No need to contact the support team for this process
※ If the following error appears, please contact your Expedia representative and request to change the rate acquisition type to “NET.”
Steps to Add a Channel
3. Enter your Expedia login credentials and click [Next].
4. Once you return to the channel list, the newly created channel will appear with the status “Enabled.”
5. On the right side of the same screen, use [Add New OTA Property] to add the Property ID registered on Expedia. This will import the listing information.
After the listing is imported, follow the steps below to synchronize rate and availability information.
Mapping pricing plans
About Expedia Synchronization Specifications
Reservations Made Before Linking to AirHost
Confirmed future reservations will be automatically imported up to 500 days in advance.
Automated Messages
Message exchanges with Expedia guests are handled via the Message API, similar to Airbnb and Booking.com.
This allows for more stable and reliable message delivery and reception than before.
However, for reservations made through affiliate sites such as Hotels.com (i.e., not booked directly via Expedia), the Message API is not supported.
If the reservation information from Expedia includes the guest’s email address, messages will be sent and received via email, rather than through the Message API.
Cancellation of Reservations
The Expedia API has more restrictions compared to other OTA APIs, and cancellation fee details are not provided via the API when a reservation is canceled.
As a result, canceled reservations will appear in AirHost with an amount of 0 in the reservation details.
If cancellation fees need to be charged, manual invoicing will be required, so please take note.
OTA Commission Fees
Expedia does not provide OTA commission fees to us via the API.
If you wish to include the OTA commission fee, please enter the percentage in the “Service Fee (%)” field, as shown in the screenshot below.
Go to [Admin Console] > [Channels] > [Select the relevant channel] > [Edit] > [Service Fee (%)].
About “Hotel Collect” (Pay at Property)
On Expedia, the “Hotel Collect” payment type includes both “AirHost Auto Payment Collection” and “Pay at Property.”
If an auto payment collection method is configured, AirHost will automatically create a payment for the corresponding Hotel Collect reservation
Help Page: Auto Payment Collection
Payment for Expedia Collect
With Expedia Collect, Expedia collects the payment from the guest first. After that, a Virtual Credit Card (VCC) is issued on or after the check-in date, and the payment can then be processed.
When configuring auto payment collection, please set “How many days before check-in should the guest be charged?” to on or after the check-in date.
If it is set before the check-in date, a payment error may occur:
“Failed to process payment for the order. Reason: This card cannot be used for transactions.”
As a result, the payment will fail, so please be careful when configuring this setting.
Refund Synchronization Specifications for Expedia
Refunds processed on Expedia fall into two categories:
Changes made by the guest themselves
Manual refunds processed by Expedia support staff
■ Actions That Are Synced to AirHost
The following actions are automatically synchronized because Expedia sends a webhook notification to AirHost:
Changes to the stay dates
Reservation cancellations
Reservation changes made by the guest
■ Actions That Are Not Synced to AirHost
The following manual refunds processed by Expedia staff are not reflected in AirHost, because Expedia does not send webhook notifications for these actions:
Refunds manually processed by an Expedia support representative
Refund adjustments internally made by Expedia through their management system
In these cases, the payment status in AirHost will not be automatically updated.
If necessary, please use “Adjust to Paid” from the reservation details page in AirHost.
Amount Differences in Expedia Reservations
Issue (Display of a Difference of 1–Several Yen)
For reservations imported from Expedia, a small difference of -1 yen to several yen may appear in the “Outstanding Balance” on AirHost.
Example:
Total Charge: ¥93,790
Total Payment: ¥93,791
Outstanding Balance: -¥1
Cause
This difference occurs due to rounding during currency conversion of tax amounts on the Expedia side.
During the process of rounding up or down fractional amounts, a difference of around 1 yen may occur.
For long stays, the rounding difference for each night may accumulate, resulting in a difference of several yen.
Handling in AirHost
AirHost cannot automatically correct or adjust this difference.
As a general rule, manual adjustments are also not supported, because if Expedia resends the reservation data, any manual changes made in AirHost may be overwritten.
Expedia treats this difference as acceptable behavior within a tolerance range, and it does not affect the actual settlement or payment.
Therefore, no special action is required on the AirHost side.
If you have any questions, please feel free to contact us using the [Ask a Question] button at the bottom right of the screen.
When making an inquiry, please be sure to include the following information.
A detailed explanation of your question
Including the property name, room type, room number, reservation number, OTA account, etc.Please include screenshots (under 20MB) that clearly show the issue and the URL of the relevant page in ONE.
Examples: screens where you are unsure how to operate, error messages displayed, OTA management page reflecting the status, etc.
Please ensure the attached images are under 20MB. If the file size exceeds this limit, we will be unable to review it and will ask you to resubmit.
Please refrain from including multiple questions or issue reports in a single inquiry.
If you have new questions, please submit them as separate inquiries.
For instructions on how to take and attach screenshots, please refer to this guide as well.












