Departures from a given stop based on static and real-time data
Request
- Base URL: https://transit.land/api/v2/rest
- URL: https://transit.land/api/v2/rest/stops/{stop_key}/departures
- Auth: none declared
Path parameters
Stop lookup key; can be an integer ID, a '<feed onestop_id>:<gtfs stop_id'> key, a Onestop ID
Query parameters
Maximum number of records to return
Search for departures on a specified GTFS service calendar date, in YYYY-MM-DD format
Search for departures on a specified calendar date, in YYYY-MM-DD format
Search for departures leaving within the next specified number of seconds in local time
Search for departures leaving after a specified local time, in HH:MM:SS format
Search for departures leaving before a specified local time, in HH:MM:SS format
Include route geometry
Use a fall-back service date if the requested service_date is outside the active service period of the feed version. The fall-back date is selected as the matching day-of-week in the week which provides the best level of scheduled service in the feed version. This value defaults to true.
Search for a specific internal ID
Search for departures on a relative date label, e.g. TODAY, TUESDAY, NEXT_WEDNESDAY
Include alerts from GTFS Realtime feeds
Pagination cursor value. This should be treated as an opaque value created by the server and returned as the link to the next result page, which may be empty. For historical reasons, this is based on the integer record ID values, but that should not be assumed to be the case in the future.
Response
ok
Changes
No recorded changes to this operation across all 1 revision of this API.