Want to receive bookings through your website?

  • We welcome new affiliates, and can set up either a white label or API for your website, or you can simply link to our websites.
  • There are no setup fees and you can trial with us and leave at any time.
  • We will share our commission with you for any bookings made or initiated through your website.
  • Many of our properties are not available to book online anywhere else.
  • Feel free to browse the technical details below, and contact us if you are interested in discussing further.


Our White Label

If you don't have your own accommodation search facility on your website, the easiest form of partnership is to set up a white label so your customers can search and book using our technology on your website. Everything is rebranded to look like part of your site using iframes, which take no time to set up. 


Our APIs

If you already have a search facility on your website, or want to develop one, we have a collection of APIs to help you integrate with your system and provide a great experience for your users.

Our APIs allow our data to be accessed by your web server, so for example your website could retrieve the availability for a hotel on a given date and display that on a web page on your site.

Our APIs are aimed at websites offering multiple vendors (e.g. hotels), rather than at individual vendor websites which are generally more suited to our White Label iframe due to the amount of time it takes to perform an API integration.


Technical Details

We are currently using two different styles of API. Our newer Affiliate Partner APIs, which are based on the Online Travel Allicance specifications (www.opentravel.org) use Soap Messaging. Our older APIs uses XML over HTTP.  To make things easier, we don't use HTTP Authentication and instead we give you a partner ID and API Key which are passed in the query string with each request. Your system can only access our APIs once we've given you your key, and none of our APIs are open for unauthenticated use. 


Our Newer Affiliate Partner APIs:

Our Newer Affiliate Partner APIs adhere to the Open Travel Alliance standards for communications. For more information check out http://www.opentravel.org/ 

OTA API Authentication


Retrieve Rooms

This endpoint is used to retrieve information on a vendor's room information. 

Specifications and Examples


Retrieve Rates And Availability

This endpoint is used to retrieve up-to-date availability and rates for room based on dates and vendors selected.

Specifications and Examples


Our Older Affiliate Partner APIs (not using SOAP):

Vendor List API

Specifications and examples

This API is used to get a list of all the vendors that are “Live” in your partner account. Adding or removing vendors is easy via our administration system, and is not currently supported by the API.

Vendors can optionally be filtered by location.

A Vendor is the generic term for a destination, business or service that we take bookings for - for example a hotel, B&B, apartment, guided tour.


Location List API (optional)

Specifications and examples

This API allows your system to get a list of all the locations we have on our system.

A Location is a predefined geographical area at the town, city or county level - for example Cheltenham (town), Bath (City), Somerset (County), Lake District (National Park). We define these locations and create new ones from time to time. Vendors can be in one or more location (i.e. Oxford and Oxfordshire). A list of locations can be obtained using our Locations API.


Vendor Details API

Specifications and examples

Use this API to get the available information for an individual vendor, including text, photos, room details, customer comments etc.


Submit Booking API

Specifications and examples

Use this API to submit a booking to us once the customer has selected their rooms on your website and are ready to proceed. There are two stages...

1.     Submit an HTTP GET request in the background from your server to ours

2.     Redirect the customer to the URL given in the XML response to the HTTP GET