-
Notifications
You must be signed in to change notification settings - Fork 41
Phone
home > Booking phase > Customer > Phone
| field | required | description |
|---|---|---|
| preferred | true or false. Is this the preferred phone number to use | |
| number | Phone number, pattern: ^[+]*[(]{0,1}[0-9]{1,4}[)]{0,1}[-\s.0-9]*$ example: +31-48934758 or +(0075)-834923384 or 020 1234 1234. In case of international usage, always provide the country code. |
|
| kind | LANDLINE or MOBILE | |
| type | PRIVATE, BUSINESS or OTHER |
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