How to enable Exely Connect
1. Send a request to сonnectivity@exely.com.
2. After your request is reviewed, we will send documentation and information for accessing a test environment to the provided email address.
3. Implement the integration on the test environment.
4. Test the integration for all points on the checklist below. For poins 1-8 of the checklist, take screenshots that clearly show that they are implemented and functioning. No screenshots are needed for points 9-13.
5. Record a video of the booking flow implementation.
Pay attention. The booking should follow the diagram below:
6. Send the screenshots and a link to the project website, where the bookings can be checked to email сonnectivity@exely.com.
7. Send a filled-in questionnaire describing your channel. For this, create a copy of the file, fill in the questionnaire and send a link to the file to email сonnectivity@exely.com.
8. We will carry out the certification within 5 working days. If all is well, we will reach out to you to sign a contract. If at least one of the checklist points is not implemented or does not work — you will need to make adjustments.
9. We sign the contract and you make the payment.
10. Within 5 working days, we add your channel to Exely Channel Manager and open it for a pilot hotel.
11. The pilot hotel selects the room types and rate plans in Exely that will be available for the channel.
12. 5 minutes after the integration is set up, the channel becomes available for booking. Exely automatically informs the channel that the hotel has made all necessary settings.
13. The integration is tested on the live environment according to the checklist (see below). Once the testing is completed, the channel is opened for connection to all hotels.
Checklist for integration testing
1. An interface is available in the channel for testing. It is possible to specify:
check-in and check-out dates,
city / property,
number of adults,
number of children,
ages of children when searching.
2. All accommodation terms are displayed when searching for available accommodations within one property: price, meal,, guest accommodation (main and extra beds).
room/type name,
accommodation price,
meal,
cancellation penalty (penalty amount, date, time, time zone of the penalty rule taking effect),
check-in/check-out time, time zone,
guests accommodation (main and extra beds).
3. There are no duplicate accommodation options in the search. All accommodation options on the test environment are unique in terms of all accommodation terms.
4. The cost of accommodation is displayed from the "priceBeforeTax" field. If the channel takes a prepayment, it must be less than or equal to "priceBeforeTax".
5. Tax should not be included in the prepayment cost and displayed in the accommodation cost. It is necessary to display taxes in a separate informative line with explanation the tax is paid at the hotel, or not to display information on taxes and fees at all.
6. It is possible to enter data for at least one guest. It is possible to enter customer data, if the customer is not the same as the guest.
7. Information for guests is displayed when at the booking stage, when calling the /bookings/verify method, a "Condition change" rejection is received — the accommodation conditions have changed. You can change the value of the "checksum" field in the “/bookings/verify” method to verify.
8. It is possible to cancel bookings. When a booking is canceled, the “calculate-cancellation-penalty” method is called and the cancellation terms for the current date are displayed correctly.
9. When using content from API, the names of properties and room types must correspond to the data from API.
10. The order of photos of a property and room types must correspond to the order passed via API. Hotel/room photos should be stored on the channel side.
11. Content and photos are stored on the channel side. When searching for prices and making bookings, Content API methods are not called and photos are not loaded from Exely.
12. Data, which are entered in the request for a booking creation, are passed via API correctly.
13. The “/bookings/verify” method must be called before the payment step. After the payment, the method for creating a booking is called.
