The first API Directory for Transport?

Devising a centralised transport operator look-up service has been an interesting output for the Open Transport initiative (as well as creating the actual customer account integration API). But it wasn’t something that we originally anticipated that we would need to do. It was just something that we identified along-the-way as being necessary for true interoperability across multiple operator accounts.

This has resulted in us publishing a draft API specification for this service here:
https://opentransport.co.uk/2019/11/04/api-specification-v0-9-1/

In the past we have compared this transport look-up service to the Sort Code or BIC/SWIFT reference used in Financial Services. This was the closest common reference we could find to describe what we wanted to do. (Yes, there are other less well-known API services in banking, such as the newer PRETA Open Banking Europe directory https://www.openbankingeurope.eu/directory/about-the-obe-directory/ )
And after some research we realised that what we actually wanted to create was something that resembled a combination of:

  1. A Sort Code / IBAN API look-up service E.g. https://www.sortcodes.co.uk/sort-codes-api
  2. The City of Los Angles transport MDS (Mobility Data Specification) reference file:
    https://github.com/CityOfLosAngeles/mobility-data-specification/blob/dev/providers.csv

So what we have actually ended up with now is (we believe) the specification for the first API Directory for Transport, delivered as an API.

%d bloggers like this: