Search for feed versions
Request
- Base URL: https://transit.land/api/v2/rest
- URL: https://transit.land/api/v2/rest/feed_versions
- Auth: none declared
Query parameters
Feed version lookup key; can be an integer ID or a SHA1 value
Feed lookup key; can be an integer ID or Onestop ID
Feed version SHA1
Feed version SHA1 of the top-level .txt files (sha1_dir)
Feed OnestopID
Filter for feed versions fetched earlier than given date time in UTC
Filter for feed versions fetched since given date time in UTC
Search for a specific internal ID
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.
Maximum number of records to return
Response format
Search radius (meters); requires lat and lon
Longitude
Latitude
Geographic search using a bounding box, with coordinates in (min_lon, min_lat, max_lon, max_lat) order as a comma separated string
Response
ok
Example response
{
"feed_versions": [
{
"earliest_calendar_date": "2020-01-01",
"feed_infos": [
{
"feed_end_date": "2019-11-15",
"feed_start_date": "2019-11-15"
}
],
"fetched_at": "2019-11-15T00:45:55.409906",
"latest_calendar_date": "2020-12-31",
"service_levels": [
{
"end_date": "2019-11-15",
"start_date": "2019-11-15"
}
],
"sha1": "ab5bdc8b6cedd06792d42186a9b542504c5eef9a",
"sha1_dir": "c1026b895dbe7476c0a6dcc1b82c909bfa952c63"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.