Skip to content

Interline Routing Platform

Intro to Interline Routing Platform

Directions by car, bike, foot, and public transit: two routing engines behind one API and one key.

The Interline Routing Platform answers the question "how do I get from here to there?" It combines a road and path router with a transit router, so an application can plan a whole journey: walking, cycling, or driving to a stop, riding transit, and walking to the final destination. Both are reached through the same endpoint and the same API key.

What you can build

Turn-by-turn directions

Plan a trip from A to B, or around any number of stops along the way, with narrative guidance ready for text-to-speech.

Transit itineraries

Plan journeys by bus, train, subway, and ferry using schedules kept current from thousands of GTFS feeds.

Matrices and isochrones

Measure travel time and distance between many locations at once, or the area reachable within 15 minutes, 30 minutes, and so on.

Map matching

Snap GPS traces and other noisy location data onto the road and path network.

Two engines, one API

Valhalla: roads and paths

Auto, bicycle, and pedestrian routing built on OpenStreetMap, with costing parameters you set per request rather than baked into the routing graph. Requests and responses follow the open-source Valhalla project, so existing clients work unchanged.

Coverage: worldwide.

Transitland Routing API: transit

Transit routing powered by the same continuously updated archive of GTFS feeds as the rest of the Transitland platform, so itineraries can be combined with queries against the other Transitland APIs. An OpenTripPlanner-compatible endpoint is available.

Coverage: the United States.

Ways to use it

Use the hosted API

We run it; you send requests. Start on the free Explorer plan; switch to Pay As You Go for commercial use, billed by usage.

Hand us the batch

Analysing travel between thousands or millions of origin and destination pairs known in advance is a different job from serving an app. We run those as a full-service engagement.

Questions & Answers

How does this relate to OpenTripPlanner?

Interline was previously more closely involved in the OpenTripPlanner (OTP) project. As of 2024 we have focused our transit-routing efforts on the Transitland Routing API, which offers an OTP-compatible endpoint. Other individuals and organizations continue to support OTP.

Do we have to use the rest of Transitland?

No. Routing is reached with a Transitland API key, and you are welcome to use it on its own. It is there if you want it: itineraries can be combined with queries against the Transitland APIs for operators, routes, stops, and schedules.

Can we host the whole platform ourselves?

The Routing Platform is a hosted service. Valhalla itself is open source and can be run on your own servers. See the intro to Valhalla for how. If you need a private deployment of the platform, contact us.

Reference documentation

Endpoints, parameters, authentication, and current limits are documented on transit.land:

Plans, pricing, and sign-up