The TOMP Working Group is pleased to announce the release of version 1.5.0 of the TOMP-API. An overview of all changes made in comparison to the previous 1.4.0 version can be found on our GitHub page.
With the release of this version, the TOMP Working Group reaffirms its commitment to facilitating smooth and efficient data exchange in the shared mobility ecosystem.
About version 1.5.0
The newly released version 1.5.0 of the TOMP-API specification contains additions that facilitate some of the actions listed in the table below:
| Operator information | Specify actions to take during onboarding, offboading, pausing and resuming. Request to pause a leg without locking the asset (closely related to the prior function). |
| Booking | Request extended expiry time during the booking process. Additional filters on the booking overview available. Provide an overview of existing damages of an asset. |
| Trip execution | Indicate battery state of charge whilst reporting progress. |
| Payment | Indicate different prices during pausing. |
The number of issues is slowly decreasing, indicating that most important scenarios are being covered. We have also added a long list of no fewer than 92 (!) (autonomous) use cases on the wiki, showing what has to be implemented when a certain functionality is required.
Many of the changes in the 1.5.0 version result from requests made by shared mobility operators and MaaS providers, and were developed further in our open-source working groups. This process makes the TOMP-API a specification that is continuously being developed in a transparent manner, considering the needs of all stakeholders.
The TOMP Working Group would therefore like to extend its gratitude to everyone who contributed to the release of version 1.5.0.
About the TOMP Working Group
The TOMP Working Group is a collaborative initiative to create a standardised language for the technical communication between Transport Operators and MaaS Providers within the MaaS ecosystem by means of an API. Its standard language describes how the different stakeholders should communicate with each other.
Our open-source Working Group is developing the TOMP-API with public and private stakeholders, aimed at facilitating the implementation of MaaS and the corresponding data exchange. The TOMP-API describes a full MaaS journey, including operator information, planning, booking, support, payments, and trip execution.