← All sources
Near real-timeLive-testedOpen collaborative platform

Mobility / Normalized departures, routing and map segments

Transitous normalized Tbilisi realtime and routing API

Transitous runs the open-source MOTIS engine over Tbilisi's static GTFS and raw vehicle-position feed. Its versioned JSON API exposes nearby stop events with both scheduled and realtime-adjusted times, stop and route metadata, journey planning, trip details, geocoding and map trip segments. It is simpler to consume than raw protobuf and does not require TTC's embedded application credential, but it is a volunteer-operated best-effort service and inherits upstream licensing and quality limits.

01

Provenance and access

How the data is reached

Unauthenticated HTTPS JSON API documented by MOTIS OpenAPI. Send a meaningful User-Agent with application name/version/contact or a browser Referer with site contact information. FOSS and non-profit use is encouraged; contact maintainers before high-volume or expensive routing use and show Transitous/source attribution.

Reuse status

Transitous has a FOSS/non-profit usage policy and attribution requirements; every underlying feed and OpenStreetMap component retains its own terms, and the TTC source license is unclear

Method
GET
Format
JSON
Authentication
None; identifying User-Agent or Referer required by policy

Accepts zoom, min/max bounds, startTime/endTime, precision and languages; this returns trip segments, not raw vehicle dots

02

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

Stop-times response

Top-level response for nearby stop events.

4 fields
Field / pathTypeNull?ExampleMeaningFreshness
stopTimes[]array<object>No5 recordsArrival and departure events around the requested pointderived
placePlace objectNo{name:"center",lat:41.72072,lon:44.74624}Requested coordinate or stop anchorNot necessarily a transit stopderived
previousPageCursoropaque stringNolong cursor tokenCursor for earlier eventsDo not parsederived
nextPageCursoropaque stringNolong cursor tokenCursor for later eventsDo not parsederived

Stop-time event

One route arrival/departure at a selected nearby stop.

24 fields
Field / pathTypeNull?ExampleMeaningFreshness
placePlace objectNoUniversity Street with event timesEvent stop and timing fieldsderived
modeenum stringNoBUSTransport modeAlso SUBWAY and AERIAL_LIFT in current APIreference
realTimebooleanNotrueWhether a realtime adjustment was appliedlive
headsignstringNoსახ.უნივერსიტეტის მ/კTrip direction or destination textreference
tripFromPlace objectNoDidi Dighomi IV Micro-DistrictScheduled trip originreference
tripToPlace objectNoTbilisi State UniversityScheduled trip destinationreference
agencyIdstringNoTTCSource agency identifierreference
agencyNamestringNoTbilisi Transport CompanySource agency namereference
agencyUrlURL stringNohttps://ttc.com.geAgency websitereference
routeIdstringNoge-tbilisi-transport-company_1:R97614Transitous-namespaced route identifierreference
routeUrlstringYesOptional agency route URLBlank in the samplereference
directionIdstringNo1GTFS trip directionreference
routeColorhex stringNo00b38bRoute display color without #reference
routeTextColorhex stringNo000000Suggested route-label text colorreference
tripIdstringNonamespaced dated trip IDSpecific scheduled trip identifierreference
routeTypeintegerNo3GTFS route typereference
routeShortNamestringNo311Passenger-facing route numberreference
routeLongNamestringNoDidi Dighomi IV M/D - Tbilisi State University H/BRoute descriptionreference
tripShortNamestringYesOptional trip number or namereference
displayNamestringNo311Consumer-facing service labelreference
pickupDropoffTypeenum stringNoNORMALBoarding and alighting rule at the eventreference
cancelledbooleanNofalseWhether this event is canceledNo cancellations observed and no Alert source existed upstreamlive
tripCancelledbooleanNofalseWhether the whole trip is canceledlive
sourcestringNo...stop_times.txt:401239:401302Source GTFS file and line provenancereference

Event Place

Stop identity, coordinates, scheduled times and current returned times nested in an event.

17 fields
Field / pathTypeNull?ExampleMeaningFreshness
namestringNoUniversity StreetStop namereference
stopIdstringNoge-tbilisi-transport-company_1:1266Transitous-namespaced stop IDreference
importancenumberNo0.0004257434MOTIS search/ranking weightNot passenger demand or social importancederived
latnumberNo41.72066WGS84 stop latitudereference
lonnumberNo44.746197WGS84 stop longitudereference
levelnumberNo0OSM or indoor levelreference
tzIANA timezoneNoAsia/TbilisiStop timezonereference
arrivalISO datetimeNo2026-07-22T09:45:00ZCurrent returned arrival, adjusted when realtime is availablelive
departureISO datetimeNo2026-07-22T09:45:00ZCurrent returned departure, adjusted when realtime is availablelive
scheduledArrivalISO datetimeNo2026-07-22T09:39:00ZOriginal scheduled arrivalreference
scheduledDepartureISO datetimeNo2026-07-22T09:39:00ZOriginal scheduled departurereference
stopCodestringNo1266Passenger-facing stop codereference
vertexTypeenum stringNoTRANSITMOTIS graph location typederived
pickupTypeenum stringNoNORMALBoarding rulereference
dropoffTypeenum stringNoNORMALAlighting rulereference
cancelledbooleanNofalseWhether the event at this stop is canceledlive
modes[]array<enum>No["BUS"]Modes serving the placereference

Map trip segment

Scheduled or realtime-adjusted segment returned by /api/v6/map/trips; not a raw vehicle dot.

12 fields
Field / pathTypeNull?ExampleMeaningFreshness
trips[]array<{tripId,displayName}>No[{tripId:"…",displayName:"439"}]Trips sharing the displayed segmentreference
routeColorhex stringNo0033b4Route display colorreference
modeenum stringNoBUSSegment modeAlso SUBWAY and AERIAL_LIFTreference
distancenumberNo1481.6848Segment distance in metresderived
fromPlace objectNoorigin stopSegment origin stopreference
toPlace objectNodestination stopSegment destination stopreference
departureISO datetimeNo2026-07-22T09:45:00ZCurrent returned departurelive
arrivalISO datetimeNo2026-07-22T09:48:00ZCurrent returned arrivallive
scheduledDepartureISO datetimeNo2026-07-22T09:39:00ZOriginal scheduled departurereference
scheduledArrivalISO datetimeNo2026-07-22T09:42:00ZOriginal scheduled arrivalreference
realTimebooleanNotrueWhether live adjustment was appliedlive
polylineencoded stringNoencoded geometrySegment geometry at requested precisionderived
03

Representative evidence

Sample records

Realtime-adjusted route 311 stop event

Retrieved 2026-07-22 13:44 Asia/Tbilisi

JSON
{
  "place": {
    "name": "University Street",
    "stopId": "ge-tbilisi-transport-company_1:1266",
    "arrival": "2026-07-22T09:45:00Z",
    "departure": "2026-07-22T09:45:00Z",
    "scheduledArrival": "2026-07-22T09:39:00Z",
    "scheduledDeparture": "2026-07-22T09:39:00Z",
    "stopCode": "1266",
    "modes": ["BUS"]
  },
  "mode": "BUS",
  "realTime": true,
  "routeShortName": "311",
  "displayName": "311",
  "cancelled": false,
  "tripCancelled": false
}
04

Boundaries

Reliability, caveats, and privacy

What held up

  • The nearby stop-times endpoint returned both scheduled and realtime-adjusted events
  • The OpenAPI schema and Transitous usage policy are public
  • Source-line provenance is included for GTFS-derived records

What can go wrong

  • Volunteer best-effort service with no TTC SLA
  • Map-wide and routing queries can be expensive; coordinate high-volume use
  • Realtime flags are derived from the raw vehicle feed and inherit its gaps
  • A realTime=false event is schedule-only, not evidence that a service is absent
  • Underlying TTC feed has no declared open-data license

Privacy boundary

  • No passenger identities or fare validations are exposed
  • importance is a routing/search score and must not be interpreted as ridership
05

Cross-source possibilities

Ideas using this source