Connect API for Transports (1.18.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. ConnectAPI for transport focuses specifically on the transport services, including primarily flights, but also trains and buses.
The API definition below is designed to handle the whole lifecycle of the transport booking process, from searching for available transports to booking and cancelling them. The key functionalities of the Connect API for transport are:
Searching for Transports: This endpoint lists all available transports based on the input criteria. Each transport comes with basic information like departure and arrival dates and times, prices, carrier name, etc.
Retrieving Transport details: This endpoint provides a detailed description of a specific transport. It requires the ID of the transport offer as input.
Checking Transport Availability: This endpoint extends the functionality above. In addition to providing transport details, it also verifies the the current status of the transport's availability. This call returns a quote ID. The quote ID is used to book the transport.
Booking a Transport: This endpoint enables booking a specific transport. It requires the ID of the transport quote and customer details for a successful booking. This call returns a booking ID.
Canceling a Transport booking: This endpoint cancels a specific Transport booking. It requires the booking ID to perform the cancellation.
| API Version | Docs Version | Changes |
|---|---|---|
| 1.0 | 01.07.2024 | Initial version |
| 1.1 | 22.01.2026 | Added streamed offers endpoint, baggage offers, transport distance, fare types, price breakdown, price per pax, passenger required fields, branded fares, seats, and ticketing limit fields |
| 1.2 | 16.03.2026 | Added AncillaryOffer, Amenity and SeatOffer schemas. Added ancillaryOffers, includedAmenities and seatOffers to TransportConnectionOfferSegment. Extended TransportBookRequest with optional ancillaries and seats selection fields |
| 1.3 | 25.03.2026 | Added AncillarySelection and SeatSelection schemas. Restructured TransportBookRequest selections into nested connections[].segments[] with per-segment ancillarySelections and seatSelections |
| 1.4 | 13.04.2026 | Added optional frequentFlyerInfo to CommonPax for frequent flyer number pass-through on booking requests |
| 1.5 | 20.04.2026 | Made Contract-Id optional, added Login and Password headers as alternative identification method |
| 1.6 | 03.06.2026 | Added required type field (AncillaryType enum: MEAL, SPEEDY_BOARDING, PRIORITY, LOUNGE_ACCESS, CHECKIN, OTHER) to AncillaryOffer |
| 1.7 | 11.06.2026 | Added optional requiredPassengerData and requiredContactData to TransportConnectionOffer using the shared Connect API objects; deprecated passengerRequiredFields |
| 1.8 | 17.06.2026 | Added BAGGAGE to the AncillaryType enum |
| 1.9 | 03.07.2026 | Made bookingClassCode optional in TransportConnectionOfferSegment |
| 1.10 | 14.07.2026 | Added optional maxPriceVariationPercentage to TransportBookRequest |
| 1.11 | 16.07.2026 | Added optional language to TransportOffersRequest |
| 1.12 | 29.07.2026 | Added optional paymentMethod to TransportBookRequest; accepted values are agreed per integration |
| 1.13 | 04.08.2026 | Added optional contact to TransportBookRequest, aligning it with the other Connect APIs |
| 1.14 | 04.08.2026 | Added the FareOffer schema and optional fareOffers to TransportOffer (branded fare tiers, availability check only), and optional selectedFareId to TransportAvailabilityRequest and TransportBookRequest. Removed the undefined fareFamily from TransportConnectionOfferSegment.required |
| 1.15 | 26.08.2026 | Added optional lastName (last name of a passenger on the booking, typically the first) to TransportRetrieveRequest |
| 1.16 | 03.11.2026 | Added optional passengers, contact, billing, paymentMethod and connections to TransportAvailabilityRequest, matching TransportBookRequest. Extracted the connections items into the ConnectionSelection and SegmentSelection schemas |
| 1.17 | 04.11.2026 | Added optional stopover to RequestTransportConnection (search only) |
| 1.18 | 05.11.2026 | Added the AncillaryOfferItem schema and optional includedItems to AncillaryOffer |
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.