-
Notifications
You must be signed in to change notification settings - Fork 41
Cope with 'Required data'
home > Booking phase > Cope with 'Required data'
If the TO requires personal data (using the conditionRequireBookingData), it must be supplied by the MP. The result should also contain the requested fields.
POST https://exampleTO.com/bookings/
{
"id": "746ac-48792bb-746dac3", ** this is the ID provided in the planning phase **
"customer": {
"id": 123456,
"firstName": "John",
"lastName": "Doe",
"phone": "tring"
}
}
The result must repeat the personal data. If data is missing, the TO should return an error state (400). see Error handling in TOMP.
If everything is correct, a booking has to be returned in state 'PENDING'. The rest of the process is described in the Booking phase.
{
"id": "746ac-48792bb-746dac3",
"customer": {
"id": 123456,
"firstName": "John",
"lastName": "Doe",
"phone": "string"
},
"state": "PENDING", ** this is a new booking in state pending **
...
}
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