-
Notifications
You must be signed in to change notification settings - Fork 41
CITYWAY
Cityway is a France-based MaaS-operator that helps Transport Authorities to implement mobility data warehouses and then build local MaaS apps on top of it. Our historical technological strength is our transit trip planner, multi-modal and predictive. We are working on aggregating mobility offers in given areas and create a mobility account that simplifies mobility for the traveler.
Here we created a generic Partner API in order to industrialize the integration of new Transport Operators.
The mobility account is one of our newest product (live in Mulhouse & beta-phase in Saint-Etienne - France).
- Unlocking a shared-car or a shared bike,
- Lifting the gate at a parking lot
- Using public transportation tickets
The traveler then pays one bill for all usages at the end of the month. He can monitor his consumptions during the month and soon he’ll be able to buy “mobility packages”.
In order to gather all those services in one app, we have to integrate the web services of all partners/transport operators.
For this we created a Partner API that helps us standardize communications with partners/transport operators.
We are here to take good ideas and share already implemented one in our projects.
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
Introduction
Scope of the TOMP-API
Versioning and releases
Process Flows
- Authentication
- Operator Information
- Privacy and Registration
- Planning Module
- Booking Module
- Trip Execution Module
- Payment Module
- Support Module
Meta-Information
Reference implementations
To-dos and risks
Technical Specifications
A1 List of terms and definitions
A2 Passenger characteristics dictionary
A3 APIs available on the transportation ecosystem
A4 Overview of the User stories
A5 Authors, Architects, collaborators and stakeholders involved
A6 Adoption and Implementation of the TOMP-API