Our two Application Programming Interface (API) specifications are currently available as Open Standards :
- Customer-account API
A standard API design for transport data sharing and therefore mobility account interoperability. Provides a consistent way for customers to integrate their MaaS or Transport provider account data ( journey, ticket and discount) with another similar account or a value-added service (e.g. a Delay Repay provider)
https://app.swaggerhub.com/apis/opentransport/customer-account/ - Centralised Operator-info API
A design for a centralised API look-up service for finding the location of data across different Transport operators and MaaS platforms. A first-of-a-kind technical directory service, based upon Internet of Things (IoT) principles, allows one Operator’s system to automatically find the latest URL of data (e.g. the Customer-account API) provided by another operator, regardless of transport mode.
https://app.swaggerhub.com/apis/opentransport/operator-info/
Additional supportive information
Open Transport Mode Definitions:
A published table of mode definitions, as used in our Open Standard:
https://opentransport.co.uk/2020/04/24/open-transport-mode-definitions/
Amendment process:
If anyone would like to consider any additions or changes to these, please see our published amendment process:
https://opentransport.co.uk/2020/02/03/amendment-process-for-our-open-standards/
Usage policy:
Both API specifications are published as Open Standards using the Apache 2.0 license. This means our work is free for anyone to use, copy and even change (as long as an accompanying Apache 2.0 license is used, the work of The Open Transport is clearly attributed and any modifications are explained)
Open Transport - Transport & Mobility Data Interoperability 