-
Notifications
You must be signed in to change notification settings - Fork 40
Customer
home > Booking phase > Customer
The Customer is (technically derived from) a Traveler. He/she has a contract with the MP.
Only the additional fields are enlisted here.
field | required | description |
---|---|---|
id | * | The identifier MaaS uses to identify the customer |
travelerReference | optional reference field to the travelers in the planning request. | |
initials | ||
firstName | First name of the customer | |
lastName | Last name of the customer | |
middleName | Middle name of the customer | |
prefix | prefix of the customer, like titles | |
postfix | postfix of the customer, like titles | |
phones | array of Phones, only one phone in this array can have a true in the property 'preferred' | |
the email address of the customer | ||
birthDate | ISO 6801 | |
address | Addresses | |
photo | base64 encoded | |
cards | Cards, containing specific information, should be the 'instances' of the card types of the traveler | |
licenses | Licenses, containing specific information, should be the 'instances' of the licenses types of the traveler |
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