Richard Hodge, Tigerbay’s Production Director, talks about how Tigerbay’s API is a central part of the technology strategy for our tour operator platform.
What is an Application Programming Interface [API]?
In its most basic form, an API is a contract that describes the interactions and resources provided by a software application. Just as a graphical user interface (GUI) makes it easier for people to use programmes, an API makes it easier for developers to use certain technologies in building applications.
Tigerbay’s API allows a tour operator’s development team, or a third party developing on their behalf, to access our reservation platform, and unlock the potential for some meaningful interactions between Tigerbay and other applications. This includes the building of transactional customer facing websites; more effective customer sales journeys; tailored management dashboards; and the development of a best of breed, integrated, end to end business solution which a customer could not build without our API.
Why is it important for a tour operator to have a platform with a strong API?
Tour operators, big and small, rely on other complimentary third party systems to complete their end-to-end business needs. Having an API which supports a wide range of functions and is easy to work with, enables this choice and flexibility, and allows us to ensure all our customers get the right solution from us.
Tigerbay is a functionally-rich reservation and e-commerce platform designed specifically for specialist travel companies. We need to meet the requirements of multiple departments and support the many activities performed within a tour operating business.
Each of our customers has a tailored solution specific to their business’s needs. At its simplest this could mean some bespoke development is needed. However, more often, a customer has a host of requirements including, integrated websites, digital marketing solutions, phone systems, links to third party campaign management tools, and distribution to metasearch and agency search tools.
Why we reinvented our API
At Tigerbay we are always looking ahead when it comes to technological developments. We keep an eye on future innovation and ensure we follow tech trends in order to stay a step ahead. This is no different when it comes to our API. We know the complex demands our customers have, and their need to stay as technically agile as possible, so we needed an API which offers them the most flexibility.
About 12 months ago, we started again and developed a brand new RESTful API based on the latest API technologies. We call it Nimble, and have invested significant time and resource in developing it as a pivotal part of our technology strategy for the future.
We adopt a “Nimble First” approach, ensuring our developments follow best practice and the strict rules that adhering to the principals REST necessitates.
For the more technically minded, it is worth checking out the well-respected Richardson Maturity Model, which breaks down the principles of a RESTful approach. Nimble attains level Three. This is the highest level achievable, and outlines our commitment to building an API that strongly adheres to these precepts. We believe that following these rules results in an API that is easier to understand, easier to extend and easier to maintain. In short, an API that is better for our customers.
What steps do you take to provide customers with the support they need to make the most out of their API?
We want to ensure that our customers’ experience is as smooth and efficient as possible. For Tigerbay, a big part of this comes from building an API that is easy to understand and navigate, and backing this up with the provision of the right tools, documentation and support, some examples of which follow.
Our use of Hypermedia within the API intuitively guides developers towards valid next steps during their interactions with Nimble (e.g. if a customer queries the system to build a Quote, one of the responses to that query might be about accessing the Passenger List. If there are no Passengers on the Quote however, that option is not valid, and therefore will not be offered.) The individual using the API should always know what they can do next without reading a document or picking up a telephone.
Documenting an API can be demanding, it is very easy for a hand-written document to fall out of sync with the ever-improving and -changing software that it seeks to support. We have tackled this through our adoption of the Swagger Framework; our documentation is an integral part of our API deployment, and allows tour operators to explore the available resources and make real API calls through a web-based interface. They can access this documentation at any time, and it is always up to date.
We also use Postman to provide our customers with fully interactive API workflows that can really kick-start integration. Our team are keen to get involved with customers early, understand where they are heading, and provide them with a workflow that delivers what they need before a line of code has even been written.
Nimble is working well. Not only do our customers’ developers and third party developers make use of it, but we use it daily to develop websites, website functionality, call centre user screens, and distribution.
But it doesn’t stop there – Nimble will continue to evolve. It gives Tigerbay and our customers the flexibility needed to meet ever-changing consumer trends and business strategies. Providing our customers with solutions perfect for them is vital to the success of Tigerbay, and at the heart of our long term relationships, and our API ensures we continue to deliver.
