FEATURE: mark booking-one-stop as reservation

[zerwuff]

API Version

from 1.5

Summary

As a MP, i want to mark an post-booking one stop with a specific reservation time, e.g. 60 minutes.
This means, the asset is reserved for 60 minutes, within this time the asset is blocked for this user.

Expected Behavior

New attribute "reserveUntil" (DateTime) at the root level for the booking request.
This would identify this booking as beeing blocked for this user to this time. After that, the booking will be cancelled if no leg is started.

Current Behavior

No API attribute exists where this reservation time can be submitted

Possible Solution

New attribute "reserveUntil" at the root level for the booking request.
Or use "metaInfo" map

Steps to Reproduce

Context (Environment)

Bike Booking and reservation of bikes (e.g. cargo pedelecs).

Detailed Description

Possible Implementation

[edwinvandenbelt]

Hello Jens! This functionality is already there, but it's in the header fields. It's called 'expires', and is in the response of the booking and onestopbooking endpoint:
responses:
"201":
description: A new booking was successfully created, status pending
content:
application/json:
schema:
$ref: "#/components/schemas/booking"
headers:
Content-Language:
$ref: "#/components/headers/language"
Expires:
$ref: "#/components/headers/expires"

Is this what you're looking for?

[zerwuff]

Hi Edwin, thanks for looking into it. As an MP, i would like to send the 'reservation' mode + reservation time already in the REQUEST. So there needs to be the information, not in the RESPOSE i think

[edwinvandenbelt]

Huh? You prescribe an expiry time as MP? Isn't that the world upside down? You get an expiry time from the TO, and if it Isn't enough, you can request additional time using the extend expiry time request.

[zerwuff]

Hi Edwin, we have 2 different use cases here

1. Instant Access Use Case:
   User is in front of bike and wants to open it right now
   MP Sends to TO:
   POST bookings-one-stop, bike opens directly (instant access)
   Lock opens instantly, user can ride. booking is confirmed.

2. Reservation Use Case:
   User opens the app and want to reserve the bike for up to 60 minutes, especially for cargo pedelecs.
   Pedelecs are rare to find (less in the fleet) and the user wants the guarantee that the bike is reserved for him.
   This means, the bike is blocked for 60 minutes for the user, a booking is created, reserving the bike for that time.
   After 15 minutes the user shows up at the bike and opens it (sends start leg)
   MP Sends to TO:
   POST bookings-one-stop (+ reservation information is needed, lock stays closed). therefore we need additional information in the request so we can decide between the 2 different use cases.
   after 15 minutes:
   MP Sends to TO:
   POST legs/{id}/events(type=SET_IN_USE)
   Lock opens directly, user can have the bike.
   If the user does not show up, booking is cancelled.

Does this explain it better?