The API to build cool stuff with public transport

Add journey planning features to your application.
Create new services using transportation data from multiple cities.
Choose either fully-free or premium access.
So, let’s...

Go for it!

Use the API

Do it the easy way! Forget the complexity of public transport data. Just drill down into features such as journey planning, line schedules, next departures, isochrons, places nearby...

Explore the API

Take away the Data

As easy as « click and download » a file, take away quality, freshness guaranted and easy to re-use transportation data into your app. Try it and see how usefull our API will be : so pick & mix data and API as you like.

Check the data

Share your work

This is an open source project! We’d love to learn about your ideas, patches, new functions, and get your comments on github. Join us on our Googlegroup, we’ll be happy to get your feedback!

Join the community
You like your city? Add it to navitia.io!
New York, San Francisco, Paris, Amsterdam, Berlin, Nantes are already available. And more to come!

If your city has OpenData public transport contact us and we will add it to navitia.io.

What is an API?

API stands for « Application Programming Interface ».

An API enables two softwares to communicate together, in the same way that telephones allow two people to talk to each other.

Mix Internet & API, and you’ve got remote calls between two softwares hosted on different servers.

What is our API for?

It is called navitia.io. It gives you anything you need to add mobility information into your application.

What is the best way for your customers to meet you?

Transit Glossary

A stop point is the physical object were someone waits for his bus (subway, or whatever type of vehicle you can have in a public transport system).
A stop area is a collection of stop points. Generally there are at least two stop points per stop area, one per direction of a line. Now think of a hub, you will have more than one line. Therefore your stop area will contain more than two stop points. In particular cases your stop area can contain only one stop point.
Some datasets do not contain any stop area.
This object links two stop points together (named origin and destination). It is the walkable part of a journey.
A journey pattern is an ordered list of stop points. Two vehicles that serve exactly the same stop points in exactly the same order belong to to the same journey pattern.
A route is a collection of journey pattern that match the same commercial direction.

Warning
The GTFS specification uses the term route for the object we call line. It does not have this notion of commercial direction.
A line is a collection of routes. Most of the time you’ll just have just two routes. This object is called route in the GTFS format.
A stop time represents the time when a bus is planned to arrive and to leave a stop point.

Getting help

All available functions are documented on the documentation.

A mailing list is available to ask question: navitia@googlegroups.com

In order to report bug or contribute on the open-source project Navitia, check our github.

At last, we are present on IRC on the network Freenode, channel #navitia.

They use navitia.io