Is your feature request related to a problem? Please describe.
Add an one-stop booking endpoint to simplify the booking process
Urgency
Major (the TOMP API works as advertised but this is really necessary to implement), because it makes it easier for PTOs and bike operators (map-oriented) to book assets.
Additional context
To increase the adoption of the TOMP-API, it would be wise to make the booking process as simple as possible.
Describe the solution you'd like
add a /bookings/one-stop endpoint, that doesn't require the offer. It should be a merge of the offer and the booking, replying directly a booked object (it has to be committed only).
Describe alternatives you've considered
Not implementing it, making it harder to implement.
Possible Implementation
POST /bookings/one-stop, with the planningRequest as body, extended with the bookingRequest fields.
Is your feature request related to a problem? Please describe.
Add an one-stop booking endpoint to simplify the booking process
Urgency
Major (the TOMP API works as advertised but this is really necessary to implement), because it makes it easier for PTOs and bike operators (map-oriented) to book assets.
Additional context
To increase the adoption of the TOMP-API, it would be wise to make the booking process as simple as possible.
Describe the solution you'd like
add a /bookings/one-stop endpoint, that doesn't require the offer. It should be a merge of the offer and the booking, replying directly a booked object (it has to be committed only).
Describe alternatives you've considered
Not implementing it, making it harder to implement.
Possible Implementation
POST /bookings/one-stop, with the planningRequest as body, extended with the bookingRequest fields.