public-api-docs

Changelog

2026-11-03

• Operations API: POST /bookings/availability/validate now returns willCauseConflict true with conflictType VEHICLE_AVAILABILITY when the booking identified by bookingId is one the planner has left unassigned or deferred and the request does not resolve that. This includes an unchanged request.

2026-11-02

• User API: POST /invoices/retry now keeps an invoice paid in the request when another invoice in the same request fails. An invoice that has no payment, or whose payment has no charge attempt, is now reported as I124 in the 400 response (I123). An unexpected failure on one invoice is now reported as I125. Before, all three cases could end the whole request in a 500.

2026-10-30

• Operations API: GET /vehicles/{id}/log-entries now returns the read-only speed, batteryVoltage and chargingState fields on each log entry. speed and batteryVoltage are omitted when the entry was written without a device reading or the device reported none, and chargingState is UNKNOWN when the vehicle had no known charging state and omitted when the entry has none stored.
• User API: Add the terms_and_conditions onboarding step type to GET /onboarding/next-step, with termsAndConditionsId and branchId identifying the document to load and accept. POST /onboarding/skip accepts terms_and_conditions, and skippable is now resolved per user: when a skip duration is configured the step is returned again once it has passed, otherwise the skip is permanent.

2026-10-29

• User API: Add the terms_and_conditions onboarding step type, returned with the termsAndConditionsId and branchId fields so the app can load (GET /termsandconditions?branchId=) and accept (POST /termsandconditions?branchId=&id=) the document. skippable is now resolved per user, and when a skip duration is configured POST /onboarding/skip only postpones the step, so GET /onboarding/next-step returns it again once the duration has passed.
• Operations API: Return the read-only completedAt date-time and completedBy user on tasks, set when the task moves to COMPLETED; neither is returned on recurring tasks or task templates. The completedByUuid request field is ignored, because the completer is always the user making the change.
• User API: POST /customers/create-or-sign-in-with-phone-number and POST /customers/create-or-sign-in-with-email-code now return 429 AUTH110 when the user is temporarily blocked after repeated failed sign-ins and asks for a new sign-in code.

2026-10-28

• Operations API: Add the optional write-only termsAndConditionsEffectiveFrom date-time to the request bodies of POST /business-units, PUT /business-units/{id}, POST /branches and PUT /branches/{id}. It sets when the terms and conditions in termsAndConditionsId start to bind users, applies only when termsAndConditionsId changes, and a missing or past value means now.
• User API: termsAndConditions now includes a read-only effectiveFrom date-time in the branch and vehicle lookups and in GET /customers/termsandconditions, but not in GET /termsandconditions/{id}. Until that date, users who accepted the Terms & Conditions in force can still rent, unless other Terms & Conditions published earlier take effect first.
• User API: POST /rentals/{rentalId}/operation can now return 412 R297 when ending or parking a rental while the bike lock is not locked.

2026-10-27

• User API: Add the optional acceptPrivacyPolicy boolean to the request bodies of POST /customers, POST /customers/create-or-sign-in-with-phone-number, POST /customers/create-or-sign-in-with-email-code and POST /customers/social-sign-up. Send true when the user accepted only the privacy policy on the sign-up screen: the new user then accepts the branch’s current privacy policy but not the Terms & Conditions, and tncAccepted is ignored. false is rejected with 400.
• User API: tncAccepted on the same sign-up endpoints now applies only when acceptPrivacyPolicy is omitted; when true (the default), the new user accepts both the branch’s current Terms & Conditions and its current privacy policy.
• User API: Terms & Conditions and the privacy policy are now versioned and resolved separately, each being the branch’s own current one, else its business unit’s. GET /termsandconditions returns the privacy fields from the privacy policy, and branchId in the response is the branch the Terms & Conditions belong to.
• User API: POST /termsandconditions also accepts the branch’s current privacy policy when the user has not accepted any yet. The id query parameter must be the branch’s own current Terms & Conditions; inherited ones are rejected with U604, so send the branchId returned by GET /termsandconditions.
• User API: GET /termsandconditions/{id} returns only the privacy fields when called with a privacy policy ID.
• Operations API: A terms and conditions record now represents one version shown together with the privacy policy published with it. POST /terms-and-conditions creates a privacy policy when a privacy field is not blank, and PUT /terms-and-conditions/{id} overwrites it, which changes it for every branch currently using that privacy policy. Privacy policies are not listed by GET /terms-and-conditions, and a privacy policy ID is not found on the /terms-and-conditions/{id} endpoints.
• Operations API: DELETE /terms-and-conditions/{id} also deletes the privacy policy published with the terms and conditions, unless a branch currently uses it, a user accepted it or other terms and conditions are published with it. It still fails with U607 when a branch uses the terms and conditions or a user accepted them.
• Operations API: Setting termsAndConditionsId on a business unit or branch now also makes the privacy policy published with those terms and conditions current, and omitting the field or sending null removes the terms and conditions together with the privacy policy. For a branch only its own terms and conditions are considered, and it falls back to its business unit’s.
• Operations API: POST /customers/{id}/accept-terms-and-conditions also accepts the branch’s current privacy policy when the customer has not accepted any yet. The optional tacId query parameter must be the branch’s own current terms and conditions; inherited ones are rejected with U604.
• User API: GET /vehicles, GET /vehicles/{id}, GET /vehicles/code/{code}, and GET /vehicles/rotating-uuid/{rotatingUuid} return the vehicle’s own position and address when physical-stations.vehicles-use-own-position is enabled. By default, vehicles at an internal physical station are still reported at the station’s position and address when docked at a port or assigned to its parking area.

2026-10-23

• Operations API: GET /vehicles/{id}/telemetry now returns windowState, sunroofState and convertibleTopState, each one of UNSET, OPEN or CLOSED. Each field is omitted when the vehicle does not report it.
• Operations API: Remove the CHECKOUT and APCOPAY values from the type field of the payment gateway configuration used by GET /pgs, POST /pgs and the other /pgs endpoints; the supported values are ADYEN, STRIPE and GOURBAN.

2026-10-22

• Device Operations API: The state object returned by GET /devices and GET /devices/{deviceId} now includes windowState, sunroofState and convertibleTopState, each one of CLOSURE_STATE_UNSPECIFIED, CLOSURE_STATE_UNKNOWN, CLOSURE_STATE_OPEN or CLOSURE_STATE_CLOSED. windowState combines all windows and is CLOSURE_STATE_OPEN as soon as one window is open.
• Operations API: POST /invoices/{invoiceId}/mark-for-collection now also accepts invoices in the DISPUTE_LOST state, in addition to EXCEPTION_SEPA, EXCEPTION_PAYING and BILLED; other states are rejected with F210.
• Operations API: POST /invoices/{invoiceId}/mark-as-lost now also accepts invoices in the DISPUTE_LOST state, in addition to EXCEPTION_SEPA, EXCEPTION_PAYING and COLLECTION; other states are rejected with F212.
• Operations API: GET /vehicles/{id}/telemetry now returns a networkSignal object with the last reported mobile network signal (strengthDbm, strengthCsq, type) and the network the device is registered on (mcc, mnc, networkName). It is omitted when the device reports none, as are any fields the device does not report.
• Operations API: GET /vehicles/{id}/log-entries now returns a networkSignal object with the same fields as the vehicle telemetry, as last known from the device when the entry was written. It is omitted for entries written without a device reading, such as manual changes of the vehicle.
• Operations API: GET /booking-stations now returns the state field for each station (IN_PREPARATION, OPERATIONAL, MAINTENANCE, HIBERNATION or OUT_OF_BUSINESS).

2026-10-20

• Device Operations API: The networkSignal object of the telemetry returned by GET /devices and GET /devices/{deviceId} now includes the network provider as mcc (mobile country code), mnc (mobile network code, without leading zeros) and networkName. networkName is absent when the code is not listed or the mnc is ambiguous.

2026-10-19

• User API: Add GET /payment/{sourceId} endpoint to retrieve a payment source by id, also after it has been deleted. A deleted source has state DELETED and a deletionReason explaining why it was removed; an unknown source returns 404 P103.
• User API: Document that pricingDetails.name of on-demand pricing options, as returned by GET /on-demand-pricing-options and in the pricingOption of rentals, is now the operator-set pricing bundle name, sent untranslated, for options sourced from a pricing bundle. It is absent when the user picked a legacy rate and on the fallback option (priceSettingId 0).
• All APIs: A request that exceeds a firewall rate limit is now answered with HTTP 429 Too Many Requests, a Retry-After header and a JSON error body with the error code RATE_LIMITED, instead of HTTP 403 Forbidden with an HTML page, as announced on 2026-10-13. Endpoint-specific 429 responses, such as AUTH227 on email sign-in, are unchanged. See Rate-limit response.

2026-10-16

• Operations API: GET /vehicles/{id}/activity now accepts the IMMOBILIZER and KEY_HOLDER values in the filters query parameter, and returns entries with these type values. For IMMOBILIZER, value is ON or OFF; for KEY_HOLDER, it is INSERTED or REMOVED.
• Operations API: Add the event types VEHICLE_IMMOBILIZER_ON, VEHICLE_IMMOBILIZER_OFF, VEHICLE_KEY_INSERTED and VEHICLE_KEY_REMOVED, which can be used as the type filter of GET /events and returned by GET /events/types.
• User API: POST /rentals/{rentalId}/driving-log/entries and PUT /rentals/{rentalId}/driving-log/entries/{drivingLogEntryId} now ignore seconds and milliseconds in startedAt when checking that it falls within the rental period; the value is stored as sent.
• User API: GET /on-demand-pricing-options now returns an empty list unless the branch operates in ON_DEMAND mode.
• User API: startedAt of driving log entries in POST /rentals/{rentalId}/driving-log/entries and PUT /rentals/{rentalId}/driving-log/entries/{drivingLogEntryId} is checked against the rental period ignoring seconds and milliseconds, and is stored as sent.

2026-10-15

• User API: POST /rentals/{rentalId}/operation with the DRIVE operation now waits up to a minute for another command on the vehicle to finish. If it is still running, the request returns 409 V448.
• User API: POST /rentals/{rentalId}/operation can now return 409 R256.12 when a DRIVE finds the rental on a different vehicle than the one it waited for.
• User API: Document the 404 response (R160.8) of POST /rentals/{rentalId}/operation when no rental with this id belongs to the user.

2026-10-14

• Device Operations API: The POST /devices/{deviceId}/execute-command response has a new field, outcome. Branch on it instead of status; errorCode still names the specific cause. The values are SUCCESS, REJECTION (a precondition on the vehicle is not met), FAULT (a hardware fault), FAILURE, UNREACHABLE, UNCONFIRMED (the vehicle may have acted, so read its state before retrying), UNSUPPORTED, UNPROCESSABLE and MISCONFIGURED. The last three are not returned yet. Treat an unknown value like FAILURE. outcome is absent when a fire-and-forget request (async: true) is answered before the command finished.
• Device Operations API: status is unchanged. It is OK when outcome is SUCCESS or absent, and ERROR otherwise. UNKNOWN and TIMED_OUT are now deprecated; they have never been returned.
• User API: Add an optional consent object with brazeConsent and appsflyerConsent (each true, false or null for not answered) to the request bodies of POST /customers, POST /customers/create-or-sign-in-with-phone-number, POST /customers/create-or-sign-in-with-email-code and POST /customers/social-sign-up. A missing or null field leaves that vendor unanswered, and the field is ignored when consent enforcement is off for that vendor on the tenant.
• User API: Add consent to PATCH /customers and to the user returned by GET /customers. On update, the fields are merged individually: a missing or null field keeps the stored answer, so an answer cannot be reset to null.
• Operations API: Add a read-only consent object with brazeConsent and appsflyerConsent to customer responses. It is ignored on update, because only the user can change it.

2026-10-13

• All APIs: Announcement — rate-limit response changes on 2026-10-19. From 2026-10-19, a request that exceeds a rate limit is answered with HTTP 429 Too Many Requests, a Retry-After header and a JSON error body with the error code RATE_LIMITED, instead of HTTP 403 Forbidden with an HTML page. The rate limits themselves do not change. If your integration detects rate limiting by the 403 status, also handle 429 before that date. See Rate Limiting.
• MaaS API: documentValidUntil in the create-verification request now also sets the customer’s licence expiry date (DRIVING_LICENSE) or ID expiry date (ANY). Once that date has passed, a VERIFIED document is set to EXPIRED_LICENSE overnight.
• User API: GET /bookings/available-stations now returns 400 when startTime lies in the past (S153) or more than two years ahead (S179), when startTime is not before endTime (S154), or when the range is longer than one year (S178).
• User API: POST /bookings/available-stations now accepts at most 10 timeSlots and returns 400 for more (S177), for a slot longer than one year (S178) or for a slot starting more than two years ahead (S179).
• User API: GET /bookings/available-stations now validates the time range. startTime must not be in the past or more than two years ahead, and endTime must be after startTime and at most one year later; violations return 400 with S153, S154, S178 or S179.
• User API: POST /bookings/available-stations now accepts at most 10 timeSlots, each at most one year long and starting at most two years ahead. Violations return 400 with S152, S154, S177, S178 or S179, and an incomplete bounding box returns S151.

2026-10-12

• Operations API: PUT /voucherables/{id} can now return 409 with error code VA133 when another save of the same voucherable is still running for more than five seconds.
• Operations API: Add settings.allowParallelBookings (boolean, default false) to user groups. When enabled, members may hold overlapping business bookings of the group that are created or edited in the back office; overlaps with personal bookings or bookings of other groups stay blocked, and bookings made in the app still cannot overlap. Omitting the field in an update keeps the current value.
• Operations API: Add optional userId and userGroupId to the request body of POST /bookings/availability/validate. With userId, the response includes a mandatory validation when the time overlaps another booking of that user. userGroupId applies only to new BUSINESS bookings without bookingId, and the overlap is not reported when all overlapping bookings belong to the same user group and it allows parallel bookings.

2026-10-09

• Operations API: Add settings.allowParallelBookings to user groups on POST /groups, PATCH /groups/{userGroupId} and group responses. When true, members can hold overlapping business bookings of the group that are created or edited in the back office; it defaults to false, and omitting it on update keeps the current value.
• Operations API: Add userId and userGroupId to the request body of POST /bookings/availability/validate. With userId, the result contains a mandatory validation if the time overlaps another booking of that user, unless all overlapped bookings are business bookings of the same user group that allows parallel bookings.

2026-10-08

• User API: GET /vehicles/{id}, GET /vehicles/code/{code} and GET /vehicles/rotating-uuid/{rotatingUuid} no longer include discounts from promotions limited to user tags the rider does not hold. The discount on the vehicle’s pricing and the DISCOUNTED value in benefits reflect only promotions the rider is eligible for.

2026-10-07

• User API: Add startedAt (date-time) to the driving log entry in the responses of GET /rentals/{rentalId}/driving-log/entries and GET /rentals/{rentalId}/driving-log/entries/{drivingLogEntryId}, and to the request bodies of POST /rentals/{rentalId}/driving-log/entries and PUT /rentals/{rentalId}/driving-log/entries/{drivingLogEntryId}, where it must fall within the rental period.
• User API: startDate on driving log entries is deprecated in favor of startedAt. Send either one in requests; if only startDate is sent, the time is derived from it.

2026-10-06

• Operations API: Add PGS_ERROR to the state values of payment attempts in Payment responses, returned when the payment provider did not report the outcome of a charge.

2026-10-01

• Platform Webhooks: Add VOUCHER_STATUS_CHANGED, published per voucher when an issued voucher’s status changes, with voucherId, userId, status (ACTIVE, EXPIRED, USED_UP, CANCELED, NOT_REDEEMED, or PENDING), and voucherableId (omitted for a custom customer-care voucher).
• User API: GeoJSON Point now requires type and coordinates. A request body with a malformed geometry returns 0018 naming the field, for example position.type.
• Operations API: GeoJSON Point now requires type and coordinates. A request body with a malformed geometry returns 0018 naming the field, for example position.type.

2026-09-30

• Authentication API: Improved documentation of API endpoints and their usage.
• User API: GET /vehicles now returns stationId for vehicles docked or parked at a physical station (numeric for internal stations, prefixed for external ones). When excludeStationedVehicles is omitted or false, a vehicle at an internal station is listed only if a rental could start there now: its slot is not out of order, and the station is operational and within its opening hours. Vehicles at external stations are not checked.

2026-09-30

• User API: Return 404 from GET /booking-price-calculator when no pricing is configured.

2026-09-29

• User API: Default max booking duration to 5 years when unset or 0

2026-09-29

• Operations API: Tasks can be patched while omitting assignee without losing task assignee, set to -1 to remove assignee.

2026-09-28

• Operations API: Update description of GET /events endpoint with more response details.

2026-09-25

• User API: Update description of GET /branches endpoint, after a bug fix.

2026-09-25

• Device Operations API: decode OKAI EB100 ECU error bitmask into telemetry diagnostics

2026-09-23

• Extend documentation of DELETE customers/{id}

2026-09-23

• Operations / Users / Maas API: Add MaaS group endpoint for partner business account management

2026-09-22

• Authentication API: document endpoint to retrieve public key to verify access and refresh tokens
• Authentication guide: add refresh token handling, logout, two-factor authentication, error handling and token signature verification
• Error codes: correct the descriptions of AUTH108 (email address not verified) and AUTH109 (refresh token invalid)

2026-09-18

• Operations API: POST /rentals can now return 409 V448 when another command is still in progress on the vehicle.
• Operations API: POST /bookings/{bookingId} can now return 409 V448 when another command is still in progress on the vehicle, or 409 V217 / V217.1 when the vehicle was reassigned or taken while the pickup was being prepared.
• User API: POST /rentals and POST /rentals/{rentalId}/operation can now return 409 V448 when another command is still in progress on the vehicle.
• User API: POST /bookings/{bookingId} can now return 409 V448 when another command is still in progress on the vehicle, or 409 V217 / V217.1 when the vehicle was reassigned or taken while the pickup was being prepared.
• Operations API: updated HTTP status of rental operations
• User API: updated HTTP status of rental operations

2026-09-17

• Users API: Add GET /front/invoices/{invoiceId} for the invoice detail view

2026-09-16

• Operations API: Customer care vouchers support a custom value and custom free minutes

2026-09-15

• User API: Add GET /bookings/cities endpoint.

2026-09-15

• User API: Add searchText query parameter to GET /branches endpoint.

2026-09-11

• Operations API: Include estimatedFee to cancellationInformation even when cancellation is disabled.
• User API: Include estimatedFee to cancellationInformation even when cancellation is disabled.

2026-09-10

• Error Codes: Add 155 error codes that production returns but the reference did not list. This closes every gap between the reference and the codes the platform emits. New sections cover the payment gateway (PGS*), physical stations and parking reservations (PS*, PR*), on-demand pricing (ODP*), driving logs (DL*), cooldowns (CD*), customer identity cards (CIC*), vehicle cards (VHCLC*), data exports (EX*), analytics (TS*), and state-of-charge levels (SLV*)
• Error Codes: Document the generic 00XX request errors, for example 0022 (parameter binding). The authentication codes of that range, 0001, 0005 and 0007, are listed under Authentication
• Error Codes: Split identity document errors into an ID Document Verification section, and credit rating errors into a Credit Rating Verification section
• Error Codes: Document that the file-access codes A103 and A105-A108 append their sub-code without a dot, for example A103416
• Error Codes: Document that core reuses 0011 and 0012 for two unrelated failures each
• Operations API: Rate limit searches of rentals, events, and message transmissions

2026-09-09

• Operations API: Rate limit /back/customers search

2026-09-07

• Operations API: Add an exact email lookup to the customer ops API

2026-09-04

• Operations API: Add appIcons to /physical-stations endpoints, optionally overriding the vehicle and/or parking icon for individual stations
• User API: Add appIcons to /physical-stations endpoints (read-only)

2026-08-31

• Device Operations API: Command error response now include failureReason (code + description, both optional, integration-scoped — match on errorCode for portable branching).
• Device Operations API: The flat errorReason field in command error response is deprecated in favor of failureReason.
• Operations API: Changes to response status codes:
  • POST /vehicles/execute-command — 200 success, 409 command already in progress, 502 vehicle refused or reported an error, 504 vehicle did not answer in time, 410 vehicle’s integration client is retired
  • POST /vehicles/{id}/command — 200 success, 409 command already in progress, 502 vehicle refused or reported an error, 504 vehicle did not answer in time, 410 vehicle’s integration client is retired
  • POST /settings-management/validate — 200 with the validation report (check the valid flag)
• Operations API: useReceiptInsteadOfInvoice is now persisted when a group is created via POST /groups; it requires a PAY_AS_YOU_GO billing cycle and is otherwise rejected with USER_GROUP_RECEIPTS_INCOMPATIBLE (UG131)
• Operations API: Documented that billingCycle is ignored on group creation (it defaults from a tenant setting) and can only be changed via PATCH /groups/{userGroupId}
• User API: Removed useReceiptInsteadOfInvoice and billingCycle from the request body of POST /groups-management; both remain read-only on group responses

2026-08-28

• User API: Add GET /pois/{poiId} endpoint (requires app=true parameter to be set)
• User API: Removed checkRentalRequirements from the request bodies of POST /groups-management and PATCH /groups-management/{userGroupId}; the field remains read-only on group responses
• Operations API: Expose a skipPreAuth flag on users and user groups that skips the pre-authorisation of funds before a rental starts
• Operations API: Skip the V2 activation check when force-deleting a user
• User API: Accept houseNumber and addressAddition when creating a group via POST /groups-management
• Operations API: Corrected the documented success response of POST /groups to 201 Created

2026-08-27

• User API: Return HTTP status code 429 instead of 500 when a sign-in code was recently issued

2026-08-26

• Users API: expose refunds, below-threshold invoices and a rental filter on /front/invoices

2026-08-24

• Platform Webhooks: Add VEHICLE_BASE_DATA_CHANGED

2026-08-19

• Operations API: Feature Parity between Price Calc Settings <> OND Pricing Bundles

2026-08-17

• Operations API: Added GET /rentals/passed-through endpoint

2026-08-14

• Operations API: Force-end accepts user GPS coordinates and processes the end rental against them
• Operations API: Support a valid-until date and a validity period together on voucherables

2026-08-13

• Operations API: Introduce extInvoiceNumber channel tracking on voucherables

2026-08-12

• Operations / Users API: Implement Rate Selector support through Pricing Bundles

2026-08-10

• Operations API: Expose free minutes on constraint vouchers in the operations API

2026-08-10

• MaaS API: Allow MaaS providers to act on business-account invoices

2026-08-07

• Operations API: expose manual verification images and info
• Operations API: expose configured max speed in vehicle telemetry
• Device Operations API: expose the currently set max speed

2026-08-03

• User API: Added excludeBookingId request query parameter to GET /bookings/dropoff-stations endpoint.
• User API: Added excludeBookingId field to request body of POST /bookings/available-dropoff-time-slots endpoint.
• Operations API: expose the failure reason for OKAI commands.

2026-07-30

• Operations API: Support custom expiry dates on customer care vouchers
• Operations API: Add pagination to verification queue endpoint

2026-07-29

• Users / Operations API: Expose migratedAt on the front and back customer GET endpoints

2026-07-22

• Users API: Expose vehicle promotions on /front/promotions endpoint
• User API: Added gender field to user registration, user update and user response.
• User API: Added read-only isBlocked and externalReference fields to the user response.
• Operations API: Added gender field to customer creation and customer response.

2026-07-20

• Users / Operations API: Expose cost sources on voucher endpoints

2026-07-20

• User API: Added excludeBookingId field to request body of POST /bookings/available-stations endpoint.

2026-07-17

• Operations API: Allow subscription purchase on behalf of end user by operator

2026-07-16

• Operations API: Support 3DS / Apple Pay user-present flow for initial subscription purchase

2026-07-08

• Operations API: Support birthdate range filter on GET /customers
• Operations API: Include rentalIds on INVOICE_CREATED webhook and /maas/invoices/{id} endpoint

2026-07-07

• Operations API: The /booking-stations/{bookingStationId}/capacity-forecast response now includes occupiedCapacity, representing the forecasted number of occupied parking spaces including out of order vehicles.

2026-07-01

• User API: Add GET /bookings/dropoff-stations endpoint.

2026-06-30

• User API: Add bookingStartTime field to AvailableDropoffTimeSlotsRequest.

2026-06-29

• Operations API: add verification queue endpoint

2026-06-25

• User API: Allow linking of files to rentals up to one hour after they were ended
• User API: Add GET /vehicles/rotating-uuid/{rotatingUuid} endpoint to look up a vehicle by its rotating public identifier
• User API: Add vehicleRotatingUuid to the rental creation request to identify the vehicle by its rotating public identifier
• Operations API: Add GET /vehicles/clusters endpoint returning vehicles aggregated into a spatial grid as a GeoJSON FeatureCollection for the service app
• User API: Add /verifications endpoints to create, list and update the current user’s manual verifications, and MANUAL verification type
• Operations API: Add write-only manualVerificationReason and manualVerificationValidUntil fields to the verification update request

2026-06-24

• Operations API: expose HDOP and individual battery info via vehicle telemetry
• Operations API: The GET /booking-stations/{bookingStationId}/vehicles endpoint will exclude outbound vehicles whose cooldown period overlaps with the specified timeframe.

2026-06-23

• Operations API: expose battery maximum capacity via telemetry

2026-06-22

• BUS-2650: add user verification flow endpoints

2026-06-22

• Operations / User API: expose free minutes on rental endpoints via applied rebates object

2026-06-18

• Operations / User API: Persist house number and address addition on business account update
• Webhooks: Create BOOKING_PICKUP webhook with additions field

2026-06-17

• Operations API: Add conflictType field to BookingTimeValidationResult.
• User API: Update description of POST /bookings/available-dropoff-time-slots endpoint.

2026-06-16

• Operations API: Add annotations to rental list response
• Operations API: Add STATION_CAPACITY_EXCEEDED type to BookingConflict object.

2026-06-12

• Users API: Add Signup flow business logic

2026-06-10

• MaaS / Operations / User API: Add optional properties houseNumber and addressAddition to user and group profile
• Operations API: Add POST /bookings/available-dropoff-time-slots endpoint
• Operations API: Smoking events

2026-06-09

• Operations API: Add cleanliness rating property to rental
• User API: Add rental cleanliness rating endpoint POST /rentals/{id}/cleanliness-rating
• Operations API: Add support for description and images to physical stations
• User API: Add description (localized) and images to physical stations

2026-06-05

• User API: Add includeEntitled request parameter to optionally include entitled additions for current user.

2026-06-03

• Operations API: Expose coordinates hdop for supported devices

2026-05-29

• Operations API: Make voucherable code optional on creation
• Operations API: Add new Device Operations API (available as value-added service)

2026-05-28

• Document api-client sign-in token behavior in OpenAPI

2026-05-28

• User API: Add maxStateOfCharge filter to GET /vehicles endpoint

2026-05-28

• Operations API: Added /booking-stations/{bookingStationId}/capacity-forecast endpoint to expose station capacity forecast.

2026-05-27

• Operations API: Added SmokeDetected and SmokeDataReady information to events

2026-05-22

• Operations API: Added /back/vehicles/open-tasks-overview endpoint to expose open tasks overview across all vehicles.
• Operations API: Added /back/vehicles/open-damages-overview endpoint to expose open damages overview across all vehicles.

2026-05-20

• Operations API: Added excludeBookingId request parameter to /back/bookings/available-categories endpoint, to support booking edit flow.
• Operations API: Added searchText filter to back/groups/{id}/members endpoint

2026-05-18

• Operations API: Removed intersectable branches setting type

2026-05-13

• Users API: Fetch rental with sql level lock on rental row before perfo…
• Operations API: Added GET /bookings/bookable-categories endpoint
• Operations API: Added GET bookings/available-categories endpoint

2026-05-07

• Users API: expose freeMinutes fields for front voucher endpoints
• Operations API: Add remainingMinutesValue to UserDetails.Statistics
• Operations API: Added GET /booking-stations/{bookingStationId}/vehicles endpoint.

2026-05-06

• User API: The includeWithPricingOnly query parameter now defaults to true (previously false). Categories without pricing configured are excluded by default.
• User API: New includeWithRentalRequirementsOnly query parameter (boolean, defaults to true) that filters results to only categories with rental requirements configured.

2026-05-05

• Operations API: Add annotations to Bookings

2026-04-30

• Operations API: Add new Benefit objects and multi-benefit related changes to the Voucherables endpoints.
• Users API: Add new POST /vouchers/redeem-code endpoint to redeem multi-benefit voucherable codes. Added missing applicablePriceType field to ConstraintVoucher.

2026-04-28

• Users API: Add acceptTnc field for email and phone otp flows

2026-04-22

• Operations API: expose refundedInvoice object in case of refund invoice

2026-04-20

• Operations API: Mark openTasks and openDamages as deprecated in VehicleList.
• Users API: Add contactInfo to response body of GET /front/branches/{id}/intersectable endpoint.

2026-04-17

• Operations API: expose state field for operator on users/subscriptions endpoint
• Users API: Add new endpoints for new subscription flow

2026-04-17

• Operations API: Enforce max group memberships when adding members via backend, add endpoint to add a single member to group.

2026-04-16

• Operations API: Document startTime query parameter, and clarify intersectTime behavior for the GET /rentals endpoint

2026-04-16

• Operations API: Expose endPosition, endAddress, endKilometers, distance, and rentalTimes for ENDED_NO_MOVEMENT rentals

2026-04-15

• Operations API: Document versionInfo in VehicleTelemetry spec

2026-04-13

• Users API: add subscription state support
• Operations API: add subscription state support

2026-04-07

• Operations API: Disallow approval of damages without severity (error code 406)

2026-04-03

• Operations API: Add searchText quey parameter to GET /iot-modules endpoint

2026-04-02

• Operations API: treat -1 as null to allow clearing station capacity on PATCH

2026-03-27

• Operations API: Add task categories
• User API: Add task categories
• Webhooks API: Add task categories

2026-03-26

• Users API: Add parking spot note at the end of rental
• Users API: move search logic into generic station get endpoint

2026-03-24

• Remove Early Pickup Penalty functionality.

2026-03-18

• User API: Add station search endpoint

2026-03-17

• User API: Parking reservation for on demand rentals

2026-03-12

• User API: updated request and response schema of various endpoints.

2026-03-12

• User API: Add /rentals/{id}/damages endpoint
• Operations API: Add “HIGH” damage severity
• User API: Add “HIGH” damage severity
• Operations API: Deprecate /booking-stations/{bookingStationId}/check-booking-creation-availability endpoint

2026-03-11

• Operations API: Add hasRatingDescription filter to /bookings endpoint
• Operations API: Allow safe replacement of IoT Modules

2026-03-10

• Operations API: Add cancelBenefits option to subscription cancel endpoint

2026-03-06

• Operations API: Add new query parameters to GET rentals/additions and GET additions-management endpoints

2026-03-05

• Operations API: Return latest invoice ID in GET /back/user-subscriptions

2026-03-03

• Webhooks: added task created webhooks

2026-03-02

• Operations API: Fix bug in deleting payment source of user group (business account) by admin

2026-02-26

• Operations API: Add excludeDecommissionedVehicles query parameter to the /vehicles endpoint.
• Operations API: Deprecate excludeRetiredVehicles query parameter in the /vehicles endpoint.

2026-02-25

• User API: Add POST /rentals/{rentalId}/files endpoint to link files to rentals in RESERVATION or ACTIVE state

2026-02-23

• Operations API: Expose list of open damages (openDamages array) in Vehicle List DTO
• Operations API: add ability to send accountId and vehicleId at the same time

2026-02-22

• Operations API: Expose list of open tasks (openTasks array) to Vehicle List DTO and deprecate openTasksCount

2026-02-20

• Moving the Voucherable validation to the Activation endpoint
• Operations API: Expose failedEndRentalRequirements for event RENTAL_END_CHECK

2026-02-19

• Remove /back/about and /back/uptime/databaseTime endpoints

2026-02-10

• User API: Filter vehicles by battery level (soc)

2026-02-05

• Operations API: Expose openingInformation and timeZoneId in list booking stations endpoint

2026-02-02

• Operations API: Add lifetimeValue and remainingVoucherValueGross fields to customer details endpoint

2026-01-26

• Operations API: expose isAccountAllowedToRent in user details response

2026-01-26

• Operations API: Vehicle bulk endpoints for tasks, notes and tags

2026-01-23

• Operations API: link files to tasks

2026-01-22

• Operations API: Expose new endpoint for vehicles bulk update by vehicle IDs

2026-01-16

• Webhooks: added task status update webhooks
• Operations API: Add branchId and includeChildBranches request parameters to KPIs endpoint

2026-01-14

• Operations API: Add information on rentals about beginner ride mode
• User API: Add beginner ride mode option on rental start

2025-12-26

• Operations API: Add all possible values to KpiType schema.

2025-12-25

• Operations API: Additional task categories (DAMAGE, ACCESS_AND_TELEMATICS, VEHICLE_FAULT, REGULATORY_AND_COMPLIANCE, BILLING_AND_CUSTOMER_CHARGE, ADMINISTRATIVE)
• Operations API: Link Damages to Issue

2025-12-19

• MaaS API: Add VERIFIED_BUT_NEEDS_CHECK value to verificationState

2025-12-18

• Operations API: Adding owner property to issue

2025-12-18

• Operations API: add detailed battery information to vehicle logs

2025-12-16

• All APIs: Extend vehicle service states - added regulatory and service-related statuses

2025-12-15

• Operations API: Add /kpis endpoint.
• User API: Add /rentals list endpoint.

2025-12-12

• Operations API: Add rating field to JsonRental schema.

2025-12-09

• Operations API: Add signupSettled query parameter to /customers endpoint.

2025-12-09

• Operations API: Add includeChildBranches query parameter to /areas endpoint.

2025-12-08

• User API: include internal addition if bookingId is passed in estimation

2025-11-27

• Webhooks: extended payload for invoice created (INVOICE_CREATED) and invoice refunded (INVOICE_REFUNDED) webhooks

2025-11-26

• Operations API: add ThoughtSpot trusted authentication endpoint
• Operations API: add endpoint to create bluetooth tokens for service workers

2025-11-20

• Operations API: Add VEHICLE_CHARGING_RESTRICTION_IGNORED enum value to Event schema

2025-11-19

• Operations API: Introduce a new benefit type for addition entitlement for voucherables and vouchers

2025-11-18

• Moved documents from knowledge base to API documentation

2025-11-18

• User API: Add missing terms and condition lookup endpoint

2025-11-17

• Operations API: Add searchText param to GET /tasks endpoint

2025-11-14

• Operations API: add pricing bundle endpoints and models in api docs- BUS-659: add pricing bundle endpoints and models in api docs

2025-11-13

• Operations API: Add searchText param to GET /damages endpoint

2025-11-11

• Operations API: Improve vehicles/execute-command documentation

2025-11-04

• Operations API: Add VehicleRentalUnavailabilityReason.

2025-11-03

• Operations API: Add ignoredRentalBlockers to VehicleListDTO.

2025-10-30

• Operations API: filter and validate additions for user and group if exists

2025-10-24

• Operations API: Add /back/additions-management endpoints for managing additions

2025-10-23

• Operations API: Add endpoint to mark invoice as LOST

2025-10-21

• Operations API: Add possibility to update Custom Tags on User Groups / Business Accounts.

2025-10-17

• Operations API: Introduced /back/business-units endpoints. Deprecated /back/revenue-centers endpoints.

2025-10-10

• Operations API: Add new vehicle service states.

2025-10-07

• Operations API: Expose pricing bundle version info in get booking by id endpoint.

2025-10-02

• Operations API: Added endpoint for calculating cooldowns (GET bookings/cooldowns).

2025-09-30

• MaaS API: Added endpoint for submission of document verifications (POST customers/{impersonationId}/verifications).

2025-09-11

• Operations API: Remove ‘PATCH verification/{verificationId}’ endpoint
• Operations API: Introduced isIncoming and isOutgoing in compatible branches endpoint, to indicate compatibility directions. Removed isCrossCompatible field.

2025-09-04

• Operations API: Add text search by Id in Rental endpoint
• Operations API: Add text search by id in Customer endpoint

2025-08-21

• Operations API: Add CORRECTION issue category
• User API: Remove includeWithPricingOnly parameter from GET /bookings/bookable-categories endpoint

2025-08-20

• Operations API: Fixed documentation of PUT vehicles/{id}/tags
• Operations API: Add Shared Booking settings

2025-08-19

• Operations API: Add cooldown data to BookingListDTO

2025-08-15

• Operations API: Add endpoint for retrieving compatible branches and endpoint for updating compatible branches

2025-08-14

• User API: Support for booking requests during booking creation

2025-08-11

• User API: Added endpoint to list bookable vehicle categories on a branch

2025-08-08

• Operations API: Allow filtering of bookings based on directions relative to the branch

2025-08-07

• Endpoint to retrieve Qlik access token- DATA-19 - Qlik Service, Controller and models

2025-08-05

• Operations API: Add startStationCooldown and endStationCooldown fields to Booking.
• Operations API: Extend GUser to contain drivingLicenseCategoryObject.

2025-08-04

• Operations API: add costSources property when creating voucherables

2025-08-01

• Operations API: Allow operator to change booking return station before and during a rental

2025-07-31

• User API: added endpoint to generate separate BLE tokens for park/drive and starting/ending a rental
• Operations API: Fix documentation for CSV import of translations

2025-07-30

• Webhooks: Added issue category to IssueCreated webhook

2025-07-25

• Operations API: Add onlyOverdueBookings filter to GET /bookings endpoint.

2025-07-24

• Operations API: Expand user details on VehicleActivityLog

2025-07-14

• Operations API: Add type field to voucherables endpoints

2025-07-09

• Operations API: Add priceGrossRaw and sumGrossRaw to RentalListDTO

2025-07-04

• Operations API: User subscriptions management new endpoints

2025-07-02

• Operations API: expose endpoint to fetch minute balance as well as monetary balance

2025-07-01

• User API: Endpoint to check requirement and surcharges at end of rental

2025-06-27

• Operations API: deprecate area parameter when adding a language

2025-06-25

• Operations API: Updated enum values of entityType

2025-06-23

• Operations API: Implement operator api to query subscriptions.

2025-06-17

• Operations API: FT-1139 Validate firstname and lastname.
• User API: FT-1139 Validate firstname and lastname.

2025-06-13

• [PLAT-1484] Record and Expose Cancellation date of Vouchers

2025-06-12

• Operations API: Add possibility to upload CSV with translations

2025-06-06

• User API: Add endBranchId to BookingUpdateRequest

2025-05-26

• Operations API: Add shouldIgnoreBCategoryRentalRequirement to user group settings
• Operations API: Add endpoint for update of driving license’s vehicle category obtainment date

2025-05-21

• User API: Add driving license’s vehicle categories to VerificationAttempt schema
• Operations API: Add driving license’s vehicle categories to VerificationAttempt schema

2025-05-20

• Operations API: add monetary field to ConstraintVoucherable and CreateVouchers

2025-05-16

• User API: Add Appsflyer support
• User API: setup Appsflyer server-2-server communication

2025-04-28

• Operations API, MaaS API: add CarLockState and IoT SoC to Vehicle

2025-04-25

• User API: Include PriceV3 and PriceV4 into Rental response
• Operations API: Include PriceV3 and PriceV4 into Rental response
• User API: Removed taxPercentage field from PriceDetails

2025-04-24

• User API: allow patching file IDs on ended rentals to upload photos etc after the rental

2025-04-22

• MaaS API: Added endpoint to retrieve MaaS Rental by ID

2025-04-02

• User API: Renamed LicenseVerificationState to DocumentVerificationState
• Operations API: Renamed LicenseVerificationState to DocumentVerificationState

2025-03-31

• User API: Added support for email OTP
• Operations API: Enable Email OTP for customer

2025-03-28

• Authentication: Added support for email OTP

2025-03-27

• Operations API: Update issue documentation

2025-03-26

• Operations API: Decrease minimum character length of firstName and lastName from 2 to 1, on user update endpoint.
• User API: Endpoint to request signed user data

2025-03-24

• Operations API: Add min amount of trips start rental requirement
• User API: Add min amount of trips start rental requirement

2025-03-13

• Extract licenseVerificationState into its own schema
• Notification channels endpoints

2025-03-10

• Operations API: Added ID Verification field to Customer List DTO

2025-03-03

• Operations API: Add support for ID verification (verification of any type of user’s personal documents)
• User API: Add support for ID verification (verification of any type of user’s personal documents)

2025-02-21

• Operations API: Support vehicle bulk creation with modules

2025-02-19

• Operations API: Added vehicle creation with module

2025-02-17

• User API: Deprecate the slots field, and expose station slots and parking area availability under a common availability field
• Operator API: CRUD API for station parking areas and new VEHICLE_IN_STATION_AREA rental end requirement. Deprecate the occupancy field, and expose new slots details and parking area details fields

2025-02-15

• User API: Add customExternalVerificationState to user
• Operator API: Add customExternalVerificationState to user

2025-02-14

• MaaS API: Expose booking id and rental id in invoice line item

2025-02-13

• Operator API: Manual credit rating of users

2025-02-12

• Added DEFLEETED as Vehicle Service State V2

2025-02-07

• Operator API: added endpoint to bulk create IoT modules

2025-01-22

• User API: updated documentation of customer endpoint responses

2025-01-13

• Operator API: Allow invoices filtering based on an invoice type: REGULAR vs. BUSINESS
• MaaS API:
  • Include business account invoices
  • Allow invoices filtering based on an invoice type: REGULAR vs. BUSINESS

2024-12-30

• User API: Added PENDING_REVERIFICATION driver’s license state to Guser response
• Operator API: Added PENDING_REVERIFICATION driver’s license state to Guser response
• MaaS API: Added PENDING_REVERIFICATION driver’s license state to Guser response

2024-12-26

• User API: Add time zone ID to branch data in booking

2024-12-20

• User API: Add time zone ID to branch data
• Operator API: Add time zone ID to branch data

2024-12-18

• Operator API: allow filtering for Bluetooth events in vehicle activities

2024-12-13

• User API: Add additional data to endpoint for searching available booking time slots

2024-12-09

• Operator API:
  • Consider vehicle in booking create/update validations
  • Include planned vehicle when listing bookings

2024-12-04

• User API: Add endpoint for calculating Booking price
• Fix minor issues with Stoplight representation of user and operations API

2024-11-29

• Operator API: On-demand pricing assignment CRUD API (option to create rate selector by assigning multiple pricing options to vehicle category on a branch)
• User API: Provide multiple on-demand pricing options for a vehicle category on a branch, and enable user to choose one of them when creating a rental.

2024-11-27

• Replace goUrban with Wunder branding

2024-11-19

• User API: Add endpoint for searching available booking time slots
• User API: Add endpoint for fetching single vehicle category

2024-10-15

• User API: Invoice data added to rental

2024-10-14

• Operator API: Allow updating of area and resetting of setting value type when updating a setting

2024-10-10

• Operator API: Expose vehicle docking/undocking on station events and details in vehicle activities

2024-10-07

• FT-25: Include userGroup on rental single endpoint

2024-10-04

• DEV-4336: Booking billing overview

2024-10-01

• DEV-4391: Add includeOnDemandOnly parameter to rentals filter

2024-09-24

• DEV-4277: Refund line item on open invoice

2024-09-23

• Formatting and minor changes in description of cancellationInformation

2024-09-17

• DEV-4276: Endpoint to list invoice line items

2024-09-13

• DEV-4297: Expose start/end branch and user group in booking endpoints of operator API

2024-09-12

• DEV-4300: Add to event dto

2024-09-09

• DEV-4262: Fetch vehicle details by qr code

2024-09-05

• Add isExtendable information to bookingListDTO

2024-09-03

• Add scheduler to trigger docking updates on failed end rentals

2024-08-30

• DEV-4210: Remove branchChangedDetails

2024-08-27

• DEV-4165: Add to openapi

2024-08-26

• DEV-4134: Fetching verification files

2024-08-09

• Add branchId to fetch balance endpoint

2024-07-31

• User API and Operator API for Physical Stations

2024-07-29

• Added ID field to balanceUpdates endpoint
• Allow operators to accept Terms and Conditions on a customer’s behalf

2024-07-26

• Added raw field for rawInvoiceDescription

2024-07-25

• Search branches inside hierarchy

2024-07-22

• Expose voucherable translation keys
• DEV-3892: Assignees full text search
• Tags and syntax errors fixes in OpenAPI spec

2024-07-20

• Support updating of the cost center of a booking

2024-07-19

• Add blockstate to MaaS GET/PATCH endpoints

2024-07-18

• Updated documentation for UserGroup Issues

2024-07-16

• DEV-3891: Add rentalId to activity response

2024-07-11

• Allow setting of type of booking when validating booking time.

2024-07-09

• DEV-3738: Add branch activity data to vehicle activities endpoint in operator API

2024-07-08

• Include vehicle categories from already created bookings

2024-07-05

• DEV-3789: Improve task fetching
• Tags and summary for booking conflicts/check-booking-creation-availability endpoints

2024-07-04

• DEV-3788: Improve damage fetching loading time
• Exclude booking from booking availability validate endpoint.

2024-07-03

• Booking created_by and updated_by.

2024-06-27

• Remove obsolete cashback

2024-06-26

• DEV-3651: Add cost center archive functionality

2024-06-21

• Missing documentation for Rating endpoints

2024-06-18

• Extend user creation through operations-api with emailIsVerified and passwordResetFlow

2024-06-13

• Terms and Conditions: possibility to reference previous version when creating new one.

2024-06-07

• Expose more vehicle events.
• DEV-3565: Expose vehicle telemetry in operator API.

2024-06-06

• Allow filtering of vehicle activities by a date parameter.
• Endpoint to validate time constraints and availability of a potential booking.

2024-06-04

• Allow changing the vehicle category of a booking in Operator API.

2024-06-03

• Assign X-th ride reward voucher on successful rental end
• Allow ignoring of time constraints on bookings for Admins

2024-05-23

• Expose additions in booking list API call
• Add price and rental distance to list booking endpoint in operator API

2024-05-21

• Add details for geofence surcharge creation

2024-05-17

• Vehicle categories search

2024-05-16

• Include category name in vehicles list response
• Include distance in rental list response

2024-05-10

• Annotation filter by type

2024-05-03

• Make branch optional for all RFID cards.

2024-04-17

• User correct user when checking terms and conditions

2024-04-16

• Check capacity issues during booking creation

2024-04-10

• Added Pricing calculator for pricing bundles

2024-04-05

• Add endpoints to properly support prolong booking

2024-04-02

• Booking conflicts

2024-03-21

• Additional fields for damages
• Overwrite pricing bundle for booking
• Booking Cancellation by operator with possibility to waive or apply booking cancellation fees

2024-03-20

• operations-api - Added missing endpoints and fixed tags and description

2024-03-18

• List vehicle cards and details for active rentals in User API
• Added possibility to specify a pricing bundle when retrieving additions to get a price estimation for a specific pricing bundle.
• Check rental start requirements

2024-03-15

• Include pricing bundles in booking station vehicle category
• Allow excluding blocked users from user search result
• Allow specifying of a vehicle already when creating a booking via Operator API

2024-03-14

• Enable filtering for users which are assigned to user-groups
• Enabled adding notes to bookings in operator API

2024-03-13

• List vehicle categories for a booking station

2024-03-12

• Expose user groups of users when searching for users in operator API
• Use UserGroupId instead of code to create bookings on operator API.
• List bookings which are active within timeframe

2024-03-11

• Manage Business Account Members for operations-api
• Booking stations overview

2024-03-07

• Update openAPI operatorId in Operator API

2024-02-28

• Allow setting of user’s desired language during user creation

2024-02-26

• Add superior email to business account member
• Expose setting of business account

2024-02-23

• Expose CreditStatus of user on list endpoint

2024-02-22

• Added Driving Log

2024-02-16

• Expose and allow setting of the language of the user

2024-02-12

• Added endpoint to set invoice to paid externally for MaaS use-case

2024-02-06

• Expose pricing details of bookings.

2024-02-02

• Provide cancellation information and potential costs of bookings

2024-01-17

• Support for multiple newsletter/marketing options

2024-01-04

• Deprecated POST customers/impersonate in favor of POST customers (createMaaSUser) of MaaS API

2023-12-28

• Added editable until to the booking response

2023-12-21

• Add support for attribute filtering in /available-categories and /availability.

2023-12-14

• Updated operations/user/maas-api

2023-11-24

• Initial documentation for user, operations and maas API.