Data Retention
Every tenant has a data-retention mode. GET /auth/check returns it as dataRetention. Adapt2Move sets the mode on request.
| Mode | What the platform stores | bookingId |
|---|---|---|
STANDARD | Bookings with driver details, price and status history | 10-character id, listed by GET /bookings |
NONE | Nothing about the booking. The provider is the only record. | Booking reference, returned once, kept by you |
NONE
POST /cars/bookings returns a booking reference as bookingId. It starts with zr1_, is encrypted and authenticated, and does not expire. It carries what later calls need to reach the provider: tenant, provider and the provider's booking reference.
Keep the reference
The platform returns the reference once and cannot look it up again. Store it with your own booking record.
GET, PATCH, POST …/cancel and POST …/vehicle-action under /cars/bookings/{bookingId} accept the reference and call the provider directly. A reference of another tenant answers 404.
GETreturns the booking as the provider reports it.driveris the operator account the booking runs on, because the driver you sent was never stored.offerPriceequalschargedRate.PATCHacceptsrentalPeriodonly. Driver details and notes are not stored, so a change to them answers400.- Cancellations and vehicle actions go to the provider. No action log is written.
These answer 403 with DATA_RETENTION_NONE:
GET /bookings: there is no booking list.- Providers that need a stored booking, for example subscriptions under
/public-transport/subscriptions. Search lists only providers that can book without one, today the Casix-based carsharing operators.