An open API standard enabling seamless communication between transport operators and mobility-as-a-service providers.
TOMP-API is an open standard API that enables technical communication between Transport Operators and Mobility-as-a-Service (MaaS) Providers. It solves the interoperability problem in the mobility sector by providing a standardized interface for integrating various transportation services, allowing users to access multiple mobility options through a single platform.
Transport operators, mobility service providers, MaaS platform developers, and organizations working on integrated mobility solutions who need standardized APIs for interoperability.
Developers choose TOMP-API because it's an open, community-driven standard that reduces integration complexity between different mobility services. Its modular design and OGC compliance ensure broad interoperability while the active working group provides ongoing development and support.
Transport Operator to Mobility-as-a-Service Provider-API development for Mobility as a Service
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The API is developed through monthly TOMP Working Group meetings, ensuring it reflects real-world needs and fosters broad adoption in the mobility sector.
Organized into base, functional, and supportive modules (e.g., Offer, Purchase, Execute, Support), allowing tailored implementations for different mobility service stages.
Includes OGC-compliant discovery endpoints as highlighted in the features, enhancing interoperability with geospatial and other standardized services.
Offers specialized API modules per transportation mode, facilitating integrated trip planning and booking across diverse mobility options.
The standard is extensive with numerous modules and some in draft (e.g., Information module), requiring significant development resources to fully adopt.
Documentation is scattered across SwaggerHub, wiki, blueprints, and meeting reports, making it difficult for new users to find cohesive guidance.
With active monthly development, the API may undergo frequent updates or breaking changes, necessitating ongoing maintenance from implementers.