-
Notifications
You must be signed in to change notification settings - Fork 41
Requiring specific data
home > Planning phase > Requiring specific data
If the TO needs personal data to validate or to contact the traveler, it can be requested in the result of the planning. Therefore the 'conditions' are introduced.
In each leg conditions can be added in the 'conditions' field. The condition needed for this purpose is the 'conditionRequireBookingData', with an array of required fields. Each field corresponds with a field in the request of the POST /bookings/. If the TO demands a specific field, the MP must supply this field in the booking request, otherwise the TO must deny the booking.
required field label | field in /bookings/ request |
---|---|
FROM_ADDRESS | from.physicalAddress |
TO_ADDRESS | to.physicalAddress |
BIRTHDATE | customer.birthDate |
customer.email | |
PERSONAL_ADDRESS | customer.address |
PHONE_NUMBERS | customer.phones, with at least one phone number |
LICENSES | customer.licenses |
BANK_CARDS | customer.cards, with at least one card of type BANK |
DISCOUNT_CARDS | customer.cards, with at least one card of type DISCOUNT |
TRAVEL_CARDS | customer.cards, with at least one card of type TRAVEL |
ID_CARDS | customer.cards, with at least one card of type ID or PASSPORT |
CREDIT_CARDS | customer.cards, with at least one card of type CREDIT |
NAME | customer.firstName AND customer.lastName |
AGE | customer.age |
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