-
Notifications
You must be signed in to change notification settings - Fork 40
BookingRequest
home > Booking phase > BookingRequest
The booking request object is relying on the outcome of the Planning result. One of the offered Bookings in the result can be booked. The id of the choosen booking should be in the booking request, along with extra information that is needed for the booking/trip execution, f.x. personal information (that's not needed for planning/routing) or information to create access data.
field | required | description |
---|---|---|
id | * | A unique identifier for the TO to know this booking by. In this phase of the booking process, the id is mandatory |
from | Place, contains the starting place. If provided, it should be the same as the starting place from the selected offer (=booking) | |
to | Place, contains the end place. If provided, it should be the same as the end place from the selected offer (=booking) | |
customer | Customer, information about the end user, who has the contract with the MP. Can be one of the Travelers | |
callbackUrl | The callback URL of the Maas Provider, to use as base url for callback, f.x. the POST legs/{id}/events and POST /bookings/{id}/events. Only to be provided when this deviates from standard or agreed URL. [v1.2.0] |
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