Transitland Scraper — Transit Data Worldwide

One actor for public transit across the whole planet — operators (agencies), routes, stops and real-time + scheduled departures for thousands of cities (Bucharest, Vienna, Barcelona, Budapest, London and many more), all from Transitland's GTFS/GTFS-RT aggregator, in one normalized schema.

Perfect for trip planners, live departure boards, transit dashboards, coverage analysis and datasets.

Bring your own key (free)

Transitland requires a free API key. Get one at https://www.transit.land/documentation#signing-up-for-an-api-key and set it in the apiKey input (stored as a secret). If the key is missing or invalid the actor logs a clear message and exits cleanly with no results (Transitland returns 401 without a key) — it never burns a run guessing.

Modes

Mode	What it returns
operators	Agencies matching a search — name, OnestopID, nested agencies, city/region/country
routes	Routes of an operator (or by search) — short/long name, type, color, agency
stops	Stops by radius (lat+lon+radius), by servedByOnestopIds, or search
departures	Real-time + scheduled departures at a stop — route, headsign, times, delay

What you get

• Operators — onestopId, name, website, agencyCount, nested agencies with places, and top-level city/region/country
• Routes — onestopId, routeId, short/long name, routeType + human routeTypeName (tram/metro/rail/bus/ferry/…), color, textColor, agency
• Stops — onestopId, stopName, stopCode, lat/lon, servedByRouteTypes, servedByOnestopIds, wheelchair boarding, place
• Departures — scheduled vs. estimated departure/arrival, departureDelay, stopHeadsign, trip & route info, scheduleRelationship

Example inputs

Find an operator

{"mode":"operators","search":"Wiener Linien","apiKey":"<your-key>"}

Routes of an operator

{"mode":"routes","operatorId":"o-u281-...","apiKey":"<your-key>","maxResults":300}

Stops near a point

{"mode":"stops","lat":"44.4268","lon":"26.1025","radius":500,"apiKey":"<your-key>"}

Live departures at a stop

{"mode":"departures","stopId":"s-...","apiKey":"<your-key>","maxResults":50}

Typical flow: operators → grab an onestopId → routes/stops → grab a stop onestopId → departures.

Output (one departure)

Fields below are the real normalizer output:

{
  "stopOnestopId": "s-u281z7-example",
  "stopName": "Karlsplatz",
  "serviceDate": "2026-07-12",
  "scheduledDeparture": "10:15:00",
  "estimatedDeparture": "10:16:20",
  "departureDelay": 80,
  "scheduledArrival": "10:15:00",
  "estimatedArrival": "10:16:20",
  "arrivalDelay": 80,
  "scheduleRelationship": "SCHEDULED",
  "stopHeadsign": "Reumannplatz",
  "stopSequence": 4,
  "tripId": "trip-123",
  "tripHeadsign": "Reumannplatz",
  "directionId": 0,
  "routeShortName": "U1",
  "routeLongName": "Leopoldau - Oberlaa",
  "routeType": 1,
  "routeTypeName": "metro",
  "routeOnestopId": "r-u281-u1"
}

Why this actor

• Whole planet, one listing — Transitland aggregates thousands of GTFS feeds into one schema.
• Departures are the wedge — real-time (estimated + delay) and scheduled times per stop, which few competitors expose cleanly.
• Reliable — cursor paging via meta.next and 429/5xx backoff.

Pricing

Pay per result — $3.00 per 1,000 results (one result = one operator / route / stop / departure). No subscription or platform fees. You supply your own free transit.land key.

Related actors

• TfL London Scraper — London Tube/bus/DLR live arrivals & line status.
• Vienna Wiener Linien — live Vienna departures & stops.

Notes & limits

• Real-time departures reflect the feed's freshness; treat each run as a snapshot.
• Independent tool built on the Transitland REST API; not affiliated with or endorsed by Transitland / Interline. You are responsible for compliant use of the output.