Create a request to create, update or cancel a booking.

Create requests retain the existing commercial-public EVSE selection behavior, including the public internal-roaming candidate pool for automatic selection. Commercial-private EVSEs can additionally be booked for users with accepted partner-invite access-policy grants for own or shared charge points. Other charging authorization does not substitute for these grants, and personal charge points are excluded. See the location check booking availability action (POST /public-api/actions/locations/v2.0/{location}/check-booking-availability) for the private eligibility policy and available slots.

An EVSE whose completed booking still has its charging session running stays occupied until the current time plus the after-booking buffer, even after that booking's end time. Create and update requests for that period are not approved on that EVSE; other EVSEs at the location can still be selected.

Update requests evaluate access for the resulting booking user: a supplied userId replaces the user for the proposed update, while omission retains the current booking user. See the update request schema for effective selection and access-rejection semantics.

A business rejection still creates a booking request and returns HTTP 201 with status "rejected" and a human-readable rejectionReason. The stored result is available through the booking request listing and read operations. Malformed input or supplied references that are unknown or invisible to the requesting admin fail validation with HTTP 422 instead; they do not create a booking request.