The Transport Operator to Mobility-as-a-Service Provider API (TOMP-API) is an open standard designed to facilitate seamless technical communication between Transport Operators and Mobility-as-a-Service (MaaS) Providers. Developed and maintained by the TOMP Working Group, the API aims to enhance interoperability within the mobility sector. For more information, visit our homepage.
TOMP-API is structured into several functional modules and extensions, each addressing a specific aspect of the interaction between Transport Operators and MaaS Providers:
Join our community for support and collaboration:
- Slack: Connect with developers and stakeholders on our Slack channel.
- Mailing List: Contact our secretariat (TOMP-Secretary@maas-alliance.eu) to join our mailing list and receive updates on working group meetings.
Working group meetings are held monthly to develop and specify the TOMP-API. All reports can be found in our meeting repository.
The working group meetings take place every month with the goal to develop and specify a generic TOMP-API for use by Transport Operators and Mobility-as-a-service Providers. All reports can be found at the documentation page.
CORE Modules:
- Offer: Enables requesting offers.
- Purchase: Facilitates the purchase of (mobility) services.
- Execute: Manages the execution phase of the trip.
Functional extensions:
- Pre sales: Allows to reserve an offer and modify it before purchasing it.
- Support: Offers customer support functionalities.
- After sales: Manages after sales processes, like refunding or revokation of tickets
Additional supportive extensions:
- Discovery: to become OGC compliant, you need to implement these endpoints.
- Customer Management: Handles user-related information and preferences. (draft).
- Information: data exhange that is not yet standardized yet (like user profiles, license and card types).
MP Module:
- Notify: the part of the API that must be implemented by the reseller/MP, to cope with messages sent by the TO or driver. It contains also confirmation and payment requests.
These modules work together to provide a comprehensive framework for MaaS integration.
The latest release of TOMP-API, version 2.0, introduces several enhancements. The 2 major enhancements are:
- OGC: Compliancy to the OGC Features standard, making it simple to use output of the API in apps or other (test) tooling.
- Enhanced Interoperability: Improved integration with other standards such as NeTEx, GTFS, APDS, and GBFS by complying to Transmodel.
These updates aim to improve user experience and broaden the applicability of the API across various transport modes.
To begin implementing TOMP-API:
- Documentation: The full version of the API is available on SwaggerHub.
- Blueprint: We've written new ones for v2, per mode: Blue prints v2
- Wiki: Explore the TOMP-API Wiki for implementation guidance.
- our quick start guide
- code-snippets: there are some code snippets (mostly Python available to speed up your implementation).
- static output: we already prepared all static output from some meta-data endpoints. You can include it directly in your solution.
This project is licensed under the Apache-2.0 License.