Connect API for Ground Transports (1.14)
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 Ground Transports focuses specifically on the ground transports services, including primarily shuttles and taxis, ferries, trains and buses.
The API definition below is designed to handle the whole lifecycle of the ground transports booking process, from searching for available ground transports to booking and cancelling them. The key functionalities of the Connect API for Ground Transports are:
Searching for Ground Transports: This endpoint lists all available ground transports based on the input criteria. Each ground transports comes with basic information like departure and arrival dates and times, prices, carrier name, etc.
Checking Ground Transports Availability: This endpoint extends the functionality above. In addition to providing ground transports details, it also verifies the the current status of the ground transports' availability. This call returns a quote ID. The quote ID is used to book the ground transports.
Booking a Ground Transports: This endpoint enables booking a specific ground transports. It requires the ID of the ground transports quote and customer details for a successful booking. This call returns a booking ID.
Canceling a Ground Transports booking: This endpoint cancels a specific ground transports booking. It requires the booking ID to perform the cancellation.
| API Version | Docs Version | Changes |
|---|---|---|
| 1.0 | 08.07.2025 | Initial version |
| 1.1 | 29.07.2025 | Added voucherUrls field to GroundTransportBooking response |
| 1.2 | 21.01.2026 | Added optional timeInterval and maxOffers parameters to search request |
| 1.3 | 26.01.2026 | Added GroundTransportSegmentCategory schema, startTime and segments to GroundTransportServiceCategory, id to GroundTransportSegmentOffer. Deprecated departureDatetime, arrivalDatetime, durationInMinutes in GroundTransportSegmentOffer |
| 1.4 | 29.01.2026 | Renamed maxOffers to maxServiceCategories in search request. Renamed startTime to departureTime in GroundTransportServiceCategory. Updated timeInterval, maxServiceCategories and departureTime descriptions. Made departureDatetime and arrivalDatetime non-required in GroundTransportSegmentOffer |
| 1.5 | 03.02.2026 | Added a new endpoint to get details of a specific offer. Extend segments to with carrierLogo and lineDetails. Extend GroundTransportRequestLocation with stationCode, cityCode, cityName, countryCode |
| 1.6 | 06.02.2026 | Extend availability request and booking request with more attributes (departureDateTime, arrivalDateTime, fareClass, carrier, etc). Extended GroundTransportResponseLocation with stationCode. |
| 1.7 | 25.02.2026 | Added travelAgentEmail, travelAgentFirstName, travelAgentLastName, travelAgencyShortName, travelAgencyEmail to Metadata |
| 1.8 | 09.03.2026 | Added includedAmenities each segment of the offer offer, added externalReference` on the service category |
| 1.9 | 20.04.2026 | Made Contract-Id optional, added Login and Password headers as alternative identification method |
| 1.9.1 | 29.04.2026 | Made connectionId required on the requests |
| 1.10 | 28.05.2026 | Added optional hotelInfo (id, name, address) to GroundTransportRequestLocation to identify hotel pick-up/drop-off points |
| 1.11 | 05.06.2026 | Added optional requiredPassengerData and requiredContactData to GroundTransportOffer to indicate which passenger and contact fields the supplier requires for booking |
| 1.12 | 19.08.2026 | Added bookable extras, mirroring the Rental Cars equipment model: GroundTransportExtra, GroundTransportExtraInclusionPolicy, ExternallyPaidCharge, ExternallyPaidChargeType and GroundTransportExtraSelection schemas, optional extras on GroundTransportOffer, optional selectedExtras on the availability and book requests. Clarified that the booking salesPrice includes the selected extras |
| 1.13 | 25.08.2026 | Added optional flightInfo (flightNumber, arrivalTime, departureTime) to GroundTransportRequestLocation, so flight-linked transfer locations carry structured flight data. Behavior change: the flight number moves from locode to flightInfo.flightNumber, with the cutover agreed per integration — see the locode description for the migration |
| 1.14 | 20.10.2026 | Added optional supplier to GroundTransportOffer, so an integration that aggregates several underlying suppliers can name the one that provided the offer |
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.