ANNEX - HOLIBOB API

1. Integration and Testing

1.1. Holibob will provide the Specification to the Partner to enable the Partner to develop the Partner Integration Code.

1.2. The Partner will develop the Partner Integration Code at its own cost. The Partner will ensure that the Partner Integration Code can integrate with the Holibob API and that it complies at all times with the Specification.

1.3. Holibob will assist the Partner in developing and testing the Partner Integration Code by:

1.3.1. making available to the Partner copies of any relevant documentation (including the Specification); and

1.3.2. making available to the Partner, from time to time, a test environment to trial Bookings.

1.4. Holibob may, at any time, change or otherwise modify the Specification without liability to the Partner. Holibob shall provide the Partner at least 30 days prior written notice of any such change, following which the Partner shall make any adjustments necessary to the Partner Integration Code at its own cost.

2. Testing and Acceptance

2.1. Holibob shall carry out such testing as is necessary and agreed between the Parties to ensure that Content can be displayed, and Bookings can be made, through the Holibob API.

2.2. Holibob will determine (acting reasonably but in its sole discretion) when relevant acceptance testing has been completed such that the Go Live Date can occur.

3. Go Live

3.1. Holibob will make available the Holibob API from the relevant Go Live Date, which will not be before the Target Go Live Date.

4. Description of Services

4.1. Through the Holibob API, Holibob shall provide the functionality for the Partner to make Bookings for Customers via the Partner Technology System.

4.2. Holibob Suppliers: If the Partner has opted to use Holibob Suppliers, Holibob shall:

4.2.1. provide and display Holibob Content on the Partner Technology System.;

 4.3. Partner Suppliers: If the Partner has opted to use Partner Suppliers, Holibob shall:

4.3.1. provide the functionality to display, and display, the Partner Content [on the Partner Technology System];

4.3.2. provide the functionality to enable Customers to make payments for Bookings through the Partner Payment Gateway, and if requested by the Partner and the payment gateway provider’s functionality permits it, ensure the integration of the Partner Payment Gateway enables the Partner to automatically transfer the relevant part of a Customer’s payment for a Booking to the relevant Partner Supplier.

5. Partner Obligations

5.1. For all Third Party Suppliers the Partner shall:

5.1.1. provide the Partner Payment Gateway and process all payments for Bookings;

5.1.2. provide booking terms and conditions which apply to a Customer’s Booking with the Partner.