To dos and risks

Opening and closing of assets can vary greatly between different transport operators. Some regard this technology as their own intellectual property and are not willing to offer external access. This is a risk for common API development and might require further harmonization in the future.
Which service/helpdesk functions are required for the User?
Options for ticketing and payment of legs/trips
Central registry of available stations/hubs/operators and assets, with unique ID’s

Blueprint for an Application Programming Interface from Transport Operator to MaaS Provider (TOMP-API) – Version Dragonfly 1

TOMP-API1

Introduction
- Roadmap
- Semantic versioning
- Use cases
- Changes per version
- Contribution
- Participants
Workflow
- Operator information
- Planning phase
- Booking phase
- Trip execution phase - start
- Trip execution phase - on route
- Trip execution phase - end
- Support
- Payment
Points of attention
- Modalities
- Specifying locations
- GDPR
Eco system
- Relations