Widely adopted > TOMP

Transport Operator Mobility-as-a-service Provider API: API standard for use by transport operators and mobility-as-a-service providers for operator discovery, trip planning, end user interaction, booking, and payment.

Package 109 stars GitHub


TOMP-API 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. Community and Support 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. Getting Started 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 here code-snippets: there are some code snippets (mostly Python available to speed up your implementation). static output: You can generate your static OGC compliancy files, use the recipe here	Base modules Offer Purchase Execute Functional additions Pre sales Support After sales Supportive modules Discovery Customer Management Information Reseller module (MP) Notify Per mode Details License Code of conduct

TOMP-API

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.

Community and Support

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.

Getting Started

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 here
code-snippets: there are some code snippets (mostly Python available to speed up your implementation).
static output: You can generate your static OGC compliancy files, use the recipe here

Base modules

Functional additions

Supportive modules

Reseller module (MP)

Notify

Per mode

Details

License

Code of conduct

Back to Transit