-
Notifications
You must be signed in to change notification settings - Fork 41
Display all assets on a map and book one of them
- You have to use the endpoint /operator/available-assets (Operator Information). In the result all physical assets are reported, including there (near) real-time locations.
- The user can select one of them on the map (you can show the information provided by the available-assets call).
- When the user decides to book it, call the endpoint /plannings/ with in the field 'use-asset' the corresponding asset-id and booking-intent=true
- There should be a result (normally one, just showing the required asset. It might be that the same asset has some different fare options, be aware of this!). Or, in case the asset has been booked just between your 2 calls, it's an empty result.
- Use the provided id in the result to book (/bookings/).
- A successful booking has to be followed with a commit of the booking, because it's still in the 'PENDING' state: /bookings/{provided id}/events { "operation": "COMMIT" }
- Now the unlocking can be done. The normal way to do this, is requesting a way to open the bluetooth device. This can be done using the /executions/{provided id}/events { "operation": "PREPARE" }. In the result there is a field 'asset-access-data', containing information to unlock the device.
- After a successful unlock, the /executions/{provided id}/events { "operation": "SET_IN_USE" } should be called, so the starting point of the leg is registrated.
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