Connect API for Rental Cars (1.4.0)
ConnectAPI is a family of APIs that standardize integration between provider and user of the services. It is designed to be RESTful, using standard HTTP methods like GET, POST, and DELETE, and it primarily exchanges data in JSON format. Connect API for Rental Cars focuses specifically on the rental car services, including cars, motorbikes and campers offered by car rental suppliers (e.g. desk-at-airport, city offices, harbour or railway stations).
The API definition below is designed to handle the whole lifecycle of the rental car booking process, from searching for available rental car offers to booking and cancelling them. The key functionalities of the Connect API for Rental Cars are:
Searching for Rental Cars: This endpoint lists all available rental car offers based on the input criteria (pickup/drop-off locations, travel period, driver age, ACRISS filters, etc.). Each rental car offer comes with basic information like pickup/drop-off location, vehicle category (ACRISS), included services, total price, cancellation policy, etc.
Getting Rental Car Offer Details: This endpoint returns the detailed view of a previously listed rental car offer. The details include the full set of equipment, included services, conditions, pictures, and the breakdown of the total price.
Checking Rental Car Availability: This endpoint extends the functionality above. In addition to providing rental car details, it also verifies the current status of the offer's availability. After the availability has been confirmed, it is expected the offer booking is ensured for a limited time, e.g. 30 minutes.
Booking a Rental Car: This endpoint enables booking a specific rental car offer. It requires the offer reference and the travelling passengers, one of them flagged as the driver, and optionally the contact person for the booking. This call returns a booking reference.
Canceling a Rental Car booking: This endpoint cancels a specific rental car booking. It requires the booking reference to perform the cancellation and may return a cancellation fee.
| API Version | Docs Version | Changes |
|---|---|---|
| 1.0 | 18.05.2026 | Initial version |
| 1.1 | 16.06.2026 | Added optional requiredDriverData field to RentalCarOffer for supplier-driven driver data requirements |
| 1.2 | 24.07.2026 | RentalCarOffer: added optional requiredPassengerData and requiredContactData. Book/Availability requests: mainContactPax is now optional (contact person) and a new required paxes list carries all travellers, one flagged as the driver (CommonPax.isDriver) |
| 1.3 | 30.07.2026 | RentalCarCancellationPolicy: rules is no longer required and must only be populated when cancellationType is FeeApplies |
| 1.4 | 05.08.2026 | Book/Availability/Cancel requests: mainContactPax is replaced by contact, typed as CommonContactDetails instead of CommonPax. The booking contact no longer carries traveller-only data (age, birth date, passport, nationality); it matches the contact field of the other Connect APIs and the fields flagged in RentalCarOffer.requiredContactData |
All API requests must be made over HTTPS.
Identification can be provided via either:
- A
Contract-Idheader identifying the contract configuration LoginandPasswordheaders for login-based authentication
The identification method should be agreed with Nezasa before integration development starts. Both methods may be provided simultaneously if required by the integration.