Skip to content

Solutions

For mobility apps

Departures, trip plans and service alerts for your product, without integrating one agency at a time.

Trusted by

  • HumanWare

Adding transit to a product is rarely one feature. It is departures at a stop, a trip plan across operators, an alert when a line is down, and the ongoing work of keeping all of it current as thousands of agencies republish their data. We run that half so your team builds the product.

What we help with

Departures riders trust

Scheduled and real-time departures for a stop, from the GTFS and GTFS Realtime feeds we already aggregate and monitor. One endpoint, whichever agencies serve that corner.

Trip planning without a routing engine

Origin-to-destination itineraries across operators, plus walking, cycling and driving legs: a hosted API rather than a routing graph you rebuild every week.

Alerts and disruptions

Service alerts alongside the departures they affect, so your product can say why a line is not running rather than quietly showing nothing.

Coverage as you grow

Launching in a new city is a query, not an integration project. The same endpoints answer wherever we already aggregate feeds.

What it runs on

Transitland APIs

REST for departures, stops, routes and operators; GraphQL when the question spans relationships.

Interline Routing Platform

Transit itineraries across the United States and street routing worldwide, behind one API and one key.

Building on your own? Start today on the free Explorer plan or Pay As You Go; plans and pricing has the details. This page is for teams past that point.

Worth reading

Outgrowing Pay As You Go, or planning a launch?

Tell us the volume and the markets, and we will size it.

Tell us about it