In order to allow testing our APIs, please login and create your personal API-Key. The key will allow to freely use the services up to a certain limit. If you want to use the APIs for production, please contact us at

Doumentation and libraries

Directly access the APIs

Most of the APIs come with a swagger documentation that gives all the information you need. You can call all libraries from each respective documentation page using the forms at the bottom of the pages. Alternatively tools like the Postman client are handy for evaluating the capabilities of the APIs.

Access the maps

Our maps are based on vector data adhering to the specifications by Mapbox. Since Mapbox is a quasi-standard for vector-based maps, there is a large number of tools to use them in applications. Since the maps are also available as raster maps in the WMTS standard there is an even larger list of tools that can display the maps.

The following list shows some of the tools and libraries that use the maps as vector tiles. Note that there are many more if you plan to use the WMTS format only.

Use our libraries

Implementation may be much easier if you use our JavaScript libraries. If you look for a low level library, written in pure JavaScript and with dependencies almost only to mapping libraries like OpenLayers or Mapbox GL JS, then mobility-toolbox-js is the way to go. If you need react components, ready to be glued together for a complete mapping application, you should give react-spatial a try.


And last but not least, some demos…


Our routing demo offers a complete UI to test the routing capabilities. You may check the mode of transport you want to route, select the hops either from form input or by clicking into the map. The routing demo also has an option for calculating the elevation profile of the route and to visualize the result graphically. Of course all stops that can be searched from the form, are backed by the stops API. Try it out.


The stops API is very useful for many applications. It is used in the routing demo, as described above. But it is also used in mapset, the editor for station plans. Most of the times, the stops API is useful as an intelligent dictionary in the back, whenever detailed information about stops is crucial.


You will find our maps in many places. Some examples are linked here.

Need help?

If you want to test the API, please login and create your own API-Key.

Please contact us if you want to use the API for production!

Feel free to reach out to the team via