Tfl

Connector for the tfl API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://api.digital.tfl.gov.uk
• Auth: query:app_key (pass your key via the apiKey input)

Operations

• accidentstats_get — GET /AccidentStats/{year} — Gets all accident details for accidents occuring in the specified year
• airquality_get — GET /AirQuality — Gets air quality data feed
• bikepoint_getall — GET /BikePoint — Gets all bike point locations. The Place object has an addtionalProperties array which contains the nbBikes, nbDocks and nbSpaces numbers which give the status of the BikePoint. A mismatch in these numbers i.e. nbDocks - (nbBikes + nbSpaces) != 0 indicates broken docks.
• bikepoint_search — GET /BikePoint/Search — Search for bike stations by their name, a bike point's name often contains information about the name of the street or nearby landmarks, for example. Note that the search result does not contain the PlaceProperties i.e. the status or occupancy of the BikePoint, to get that information you should retrieve the BikePoint by its id on /BikePoint/id.
• bikepoint_get — GET /BikePoint/{id} — Gets the bike point with the given id.
• cabwise_get — GET /Cabwise/search — Gets taxis and minicabs contact information

Inputs

• apiKey — your tfl API key
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: accidentstats_get
apiKey: <your key>