-
Notifications
You must be signed in to change notification settings - Fork 40
Planning result
home > Planning phase > Planning result
field | required | description |
---|---|---|
validUntil | * | format:
|
options | * | the list of possible options (of object booking ) this TO can deliver. It is dependent on the query-parameter booking-intent how accurate the result can be. In case of true , the results must contain an ID, to refer to in the booking phase and contains trustable information, with an accurate price (to be paid by the MP to the TO). |
Each result in the 'options' array is a complete booking object.
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