Corporate

Travelflow Integration Guide

Step-by-step instructions to aid you in integration

Introduction

The Travelflow Web Booking Engine is a ready-to-go booking solution that can be implemented into any website with ease. That means, no need to redesign your website and no hassle.

Your web developer can implement the booking engine into your site following our step-by-step guide, or alternatively, our in-house team can incorporate it into your site for a small fee.

Looking for the Leisure guide?

Table of Contents

Add the booking engine to your website

The Travelflow Web Booking Engine can be implemented into your site in just a few simple steps:

Step 1: Position the booking engine

Insert the HTML shown to the right into the position where you would like the booking engine to appear on your web page.

If you are using a CMS such as WordPress or similar you can add this code through the built in page editor.

The data-ibe-url attribute can be customised to show different aspects of the booking engine.

The &bn=0001 query string denotes the booking engine branch number.
This can be used to load a specific branch onto your web page.

If you only have a single branch this can be safely omitted.


                  

Step 2: Initialise the booking engine

Add the following JavaScript code to your page just before the closing </body> tag.

Before saving any changes remember to make sure that :

  • https://example.com/ is replaced with your Booking Engine URL.

Please contact our Customer Support team at support@billian.co.uk if you haven’t already received this via e-mail.

Only one copy of the integration script is required for any number of booking engines on a single page.


                  

Implement the results page

Step 1: Create a results template

Searches made through the booking engine generate results that can appear on a separate page to match the look and feel of your website.

To implement this you will need to provide a simple results template for the booking engine to use.

The results page should only serve to display results from the booking engine, and should consist of a header, a footer and no body content whatsoever.

The results page should be directly accessible from any internet browser, even though it may not be linked to your website.

See the next step for example code

Flight Deck web settings

Example of a results template. View it here.

Step 2: Adding the template tag

Add your template tag to the main content, as shown.

The template tag is mandatory because this is what’s targeted and replaced by the Travelflow Web Booking Engine to display results.

Shown here is example code of a results page - (your page will likely be more complex)

Note: ##BookingEngine## is the default template tag and can be changed to anything you like, as long as it is mirrored in Flight Deck.


                  

Configure Flight Deck

Flight Deck is your Web Administration tool for the Travelflow Web Booking Engine.

Contact our Customer Support team at support@billian.co.uk to be provided with a URL and credentials for Flight Deck, if you don’t already have this information.

Step 3: Login to Flight Deck

  • Navigate to your Flight Deck URL.
  • Login using the username and password you have been provided with.

Note: If you have multiple branches you will be given the option to select a branch on the login page.

Contact our Customer Support team at support@billian.co.uk if you are missing any of this.

Flight Deck login page

Step 4: Add your results template URL into Flight Deck

Once logged in, from the dashboard navigate to "Web Settings" and click on the "Look & Feel" tab.

  • Enter the URL for the results page into the "Template URL" field
  • Enter the template tag you added to you template in the "Template Tag" field
  • Save the changed settings

Note: You can save changes to any page in Flight Deck by clicking the green tick button in the top right of the page.

Once this has been completed, any new searches performed on the Travelflow Web Booking engine will appear contained in your results template.

Any issues with how the template looks after perfoming a search can usually be solved by clearing the template cache. To clear the template cache you can click the red "X" icon next to the "Template URL" field in Flight Deck.

Flight Deck web settings

Recommendations

Listed below are some recommendations that can help with the integration of the booking engine into your results template.

Simplify the the results template

To minimise any possible conflicts between the booking engine and your template, avoid using unnecessary scripts, libraries, forms or analytics code where possible.

  • If possible, try to use absolute paths for any images, links or external files on the page containing the ##BookingEngine## tag.

Note: If you use a CMS (such as Joomla! Or Wordpress) there are plug-ins available to allow you to disable the built-in scripts / javascript libraries on certain pages.

CORS (cross-origin resource sharing)

After implementing the results page, icons from your template page may not display correctly after performing a search on the booking engine.

This is not unexpected and is due to how web browsers handle certain file requests. For more information and how to resolve this, read below.

Understanding CORS

The same-origin policy is an important security concept implemented by web browsers to prevent certain code from making requests against a different origin (e.g. a different domain) than the one from which it was served.

A request for a resource (like an image or a font) from one website to another website is known as a cross-origin request. CORS (cross-origin resource sharing) manages these cross-origin requests.

Although the same-origin policy is effective in preventing resources from different origins, it can also prevent legitimate interactions between a server and clients of a known and trusted origin.

Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional HTTP headers to tell a browser to relax the same-origin policy so that a web application running at one origin (domain) can have permission to access selected resources from a server at a different origin.

How do I implement CORS?

Unfortunatly there is no single solution to this, and implementing the request headers to set up CORS correctly depends on the language and framework of your backend solution.

For example, if you are using an Apache web server with WordPress for your website, this could be a simple as adding the following line to your sites .htaccess file.

Note: Typically the .htaccess file will be in located in your websites root directory.

Locations can vary from host to host. If in doubt, contact your hosting provider.

Once the correct request headers have been set on your server any icons from your that couldn't be displayed should work correctly after refreshing the page.

For other configurations, a great resource is the Enable CORS site which has more information on how to setup CORS.


                  

Support

If you are having any issues implementing any of the steps here, contact our Customer Support team at support@billian.co.uk.

We also offer an integration service where our in house developers work closely with your team to integrate the Travelflow Web Booking Engine into your site, for more information, get in touch.