TOMP
An open API standard enabling seamless communication between transport operators and mobility-as-a-service providers.
What is TOMP?
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.
Overview
Transport Operator to Mobility-as-a-Service Provider-API development for Mobility as a Service
Use Cases
Best For
- Building integrated mobility platforms that combine multiple transportation services
- Transport operators wanting to expose their services to MaaS providers
- MaaS providers needing standardized APIs to integrate with various transport operators
- Developing OGC-compliant discovery mechanisms for mobility services
- Creating multi-modal trip planning and booking systems
- Implementing standardized customer management and support systems for mobility services
Not Ideal For
- Companies seeking a turnkey, plug-and-play API solution without any development effort
- Projects focused exclusively on a single transport mode with no need for cross-operator interoperability
- Startups or teams with tight deadlines that cannot invest in implementing a comprehensive standard
- Organizations preferring proprietary, vendor-specific APIs for deeper integration and dedicated support
Pros & Cons
Pros
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.
Cons
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.
Frequently Asked Questions
Related Projects
MDSA data specification to enable right-of-way regulation, digital policy, geofencing, and two-way communication between mobility companies and public agencies worldwide for any regulated, shared, or agency vehicle.
gbfs R packageAn R package to interface with bikeshare data!
NeTexA general purpose XML format designed for the exchange of complex static transport data among distributed systems managed by the CEN standards process
DATEXEU data standard for road traffic and travel information
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.