-
Notifications
You must be signed in to change notification settings - Fork 41
Trip execution phase end
home > Trip execution phase > End
Whenever the leg is ended, the asset can be locked again by using the app. The app has to inform the MP that the trip is finished (offline scenario). The MP has to send it to the TO.
POST https://exampleTO.com/legs/746ac-48792bb-746dac3/events/
{
"operation": "FINISH",
"asset": {
"assetId": "bike1",
"place": {
"coordinates": {
"lng": 6.169639,
"lat": 52.253279
}
}
}
}
In case of an online scenario the same message has to be send to the MP, this one send it to the TO and the TO should lock the bike.
POST https://exampleTO.com/legs/746ac-48792bb-746dac3/events/
{
"operation": "FINISH",
"asset": {
"assetId": "bike1",
"place": {
"coordinates": {
"lng": 6.169639,
"lat": 52.253279
}
}
}
}
In some cases, the asset or TO will send the finish message to the MP (train, metro, ...). In that case, the MP shouldn't pass on the message to the TO of course.
It could be needed to have a 'FINISHING' state, where the asset is ending up the leg. Therefore this operation is also in the API.
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