Finding Multi-Stop Flights Using Neo4j & Python 🐍 Part #2
In this blog-post, I’d like to give you a first introduction on how we can search for flights using Python and the Kiwi API. Excited? Let’s get started💻🖱️.
This post is part of a series of posts. I highly recommend to also check out the previous post, in case you haven’t been following along from the start.
Finding the right API for our project, a bit of history
One of the best remaining API’s out there are the Skyscanner and Kiwi (formerly known as Skypicker) API. Both APIs are well documented and even offer python wrappers. I’ll be using the Kiwi API, as their data seems more accurate and they are combining legacy carriers and low-cost carriers onto a single ticket, which is something Skyscanner still struggles with. The later was something I definitely wanted to have in my project, as it seems crucial if you want to travel really CHEAP. Another two reasons why I went for the Kiwi API is because it’s blazing fast and they have a partner key, which can be used for testing. If you want to Skyscanner you’ll have to apply for your own API-key right-away here: Link to Skyscanner.
Our first flight search
Searching for a flight using the Kiwi.com API is really straight forward. First, you’ll have to set up the kiwi.com Python Wrapper. Once everything is in place we can start right away.
At first we need to create an instance of the Search class.
And then we can start with passing our airports and dates to the search_flights function. In my example, I am searching for a flight from Frankfurt (FRA) to New York (JFK). Please note that the dates have to be specified in the format day/month/year, which is different from the US date format. We also have to specify a partner, which works similarly to an API key. For testing, we’re free to use picky.
You might also want to add the parameter sort='price’, that way you’ll get the cheapest flights first. The limit-parameter can also be quite handy if you’re only interested in retrieving a few data sets rather than everything. For all the additional parameters check out their documentation. A word of caution: the way kiwi works is that it’s searching for a one-way flight by default. if you want to search for a return or multi-stop flight you’ll have to define each segment using separately, like this:
The data returned by the API is a properly formed JSON with the following syntax.
The actually interesting part lives within the data array. The data array is home to the information like the price, a deep link (the site where you can actually book the flight) and a lot of additional information like the distance, the operating airline and most importantly the segments of the journey (which we’ll need them later on). We can loop over the data fairly easily using Python’s “for in”-function.
In the snippet above I am also printing the individual legs of the journey, the total price and the total distance. The data for the individual legs are stored in the sub-array with the key route.
If everything is working as expected, your console output should look similar to this screenshot.
That’s it for this brief introduction. In the nex post, I’ll introduce you to the concept of hidden city ticketing, why we are particularly interested in it, why it’s a really powerful tool. We’ll use what we’ve learned today to find hidden city flights the python way.