Bookings

IMPORTANT NOTE: Depending on your integration strategy, you may choose to map some of ID-s to your system ID-s (e.g. car categories, offices, equipment, pricelists). If you do that, please note that ID-s WILL BE DIFFERENT ON PRODUCTION AND TEST ENVIRONMENTS, so you should make it easily configurable on your side.

Basic booking flow follows three steps:

Basic steps

1. Availability check

To begin, check which car categories are available using "booking/availability" method.

Availability request example

URL: https://{provider host}/{culture}/api/bookings/availability

URL example: https://demo.s2.renteon.com/en/api/bookings/availability

HTTP method: POST

HTTP headers:
Authorization: Bearer {access token goes here}
Content-Type: application/json

Params format: BODY: application/json

Params:

{
    "BookAsCommissioner": false, 
    "OfficeOutId": 3,
    "OfficeInId": 3,
    "DateOut": "2026-06-15T03:01:33",
    "DateIn": "2026-06-16T03:01:33"
}

For details please check corresponding reference page.

2. Create new booking

Client uses response information from availability check to create new booking using "bookings/create" method. Method returns in memory representation of booking model, which is not yet saved. Booking model holds information about price and mandatory fees. It also holds list of optional services client may choose at will (equipment, insurance, etc.).

For details, please check API reference.

Booking create request example

URL: https://{provider host}/{culture}/api/bookings/create

URL example: https://demo.s2.renteon.com/en/api/bookings/create

HTTP method: POST

HTTP headers:
Authorization: Bearer {access token goes here}
Content-Type: application/json

Params format: BODY: application/json

Params:

{
	"CarCategoryId": 1,
	"OfficeOutId": 3,
	"OfficeInId": 3,
	"DateOut": "2026-06-15T03:01:33",
	"DateIn": "2026-06-16T03:01:33",
	"PricelistId": 91,
	"Currency": "EUR"
}

For details please check corresponding reference page.

IMPORTANT NOTE: You can modify "booking/create" and "booking/open" reponse model properties, and use it as input for "booking/save" or "booking/calculate" methods. There is no need to create new models, since extra properties in input model will be ingored by API.

2.1. Recalculate the booking (Optional)

Client may choose to recalculate the booking using "booking/calculate" method. Calculate can be called to get new pricing and other information after changing some properties, like:

selecting some optional services
changing drivers information
changing booking period, etc.

Method returns in memory representation of booking model, which is not yet saved.

For details please check corresponding reference page.

2.2. Selecting optional services / additions (Optional)

Client may select/unselect any optional additional services or equipment (e.g. baby seat, insurances, etc.). To do so, simply modify BookingModel > Services > IsSelected property to true or false and update Quantity property before calling calculate or save methods.

For details, please check BookingInModel, and BookingModel.

3. Save the booking

Client uses booking model (response of "create" or "calculate" methods) to save the booking using "bookings/save" method. Booking model can be modifed to select additional services, update client name, etc.

For details please check corresponding reference page.

Other operations

Bookings controller provides additional operations:

search - to retrieve list of previous bookings
open - to retrieve detailed boooking information, or to modify it
cancel - to cancel boooking

For details, please check API reference.