Transit Routing
Next Nearby Departures (Deprecated)
All Next Departures
- All Next Departures By Geocoord
- All Next Departures By Station IDs
Station Search
Response Data Types
- AP
- AccessPoints
- Act
- Activities
- Addr
- Addresses
- Alert
- Alerts
- AltDep
- Arr
- At
- Attributions
- Branding
- Cities
- City
- CityCount
- Connection
- Connections
- Coverage
- Cvg
- Dep
- ExploredCoverage
- Fare
- Fares
- Freq
- Graph
- Guidance
- Info
- Instruction
- IsoDest
- Isochrone
- Journey
- LineInfo
- LineInfos
- LineSegments
- Link
- LocalCoverage
- Logos
- Maneuver
- Maneuvers
- Message
- MissingCoverage
- MultiNextDeparture
- MultiNextDepartures
- NearbyCities
- NearbyCoverage
- NextDepartures
- Op
- Operators
- PathSeg
- PathSegments
- Pop
- Pr
- Providers
- RT
- RefPathSeg
- Res
- Sec
- Sections
- Stations
- Stn
- Stop
- Summary
- Tariff
- Transport
- Transports
Simple Types
- ActIds
- AttributesIds
- Boolean
- Color
- Coordinate
- Date
- DateTime
- FareReason
- IdListBranding
- IdListOp
- IdListTransport
- Level
- LineSegmentsType
- LinkIds
- ModesList
- RPrice
- RangePrice
- StationId
- TimeDelta
Error Handling
- Error Codes

Public Transit API v3 Developer's Guide

Response Data Types

This section provides a reference to the data structures used in responses to requests to the Public Transit API v3 resources.