How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TUI Group Booking/segments API

The booking/segments API from TUI Group — 7 operation(s) for booking/segments.

TUI Group Booking/segments API is one of 113 APIs that TUI Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include booking/segments. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 7 paths, and defines 46 schemas. It is described by OpenAPI 3.2.0, at version 4.8.6.23.

Requests are made against 2 base URLs: https://prod.api.tui/flight/newskies/rest, https://playground.api.tui/flight/newskies/rest.

9 operations 7 paths 46 schemas 3 DELETE2 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.8.6.23
Base URL
https://prod.api.tui/flight/newskies/rest
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

TUI Group Booking/segments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (jwt) (JWT). By default, every request must be authenticated.

  • JWT — Paste your JWT token from the token endpoint.

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 3 DELETE, 2 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

booking/segments 9
DELETE
/api/nsk/v1/booking/segments/{segmentKey}
Cancels the specific segment from the booking in state.
nsk_v1_booking_segments_segmentKey_delete 1 param → 200403409
DELETE
/api/nsk/v1/booking/segments/{segmentKey}/classOfService
Restores a segment to the class of service prior to an upgrade or downgrade.
nsk_v1_booking_segments_segmentKey_classOfService_delete 2 params → 200409
GET
/api/nsk/v1/booking/segments/{segmentKey}/passengers/{passengerKey}
Gets a specific passenger segment from the booking in state.
nsk_v1_booking_segments_segmentKey_passengers_passengerKey_get 2 params → 404200
POST
/api/nsk/v1/booking/segments/{segmentKey}/passengers/{passengerKey}/infant
Creates an infant on a passenger in the specified segment.
nsk_v1_booking_segments_segmentKey_passengers_passengerKey_infant_post 2 params body → 201409
DELETE
/api/nsk/v1/booking/segments/{segmentKey}/passengers/{passengerKey}/infant
Deletes an infant from a passenger in the specified segment.
nsk_v1_booking_segments_segmentKey_passengers_passengerKey_infant_delete 2 params → 200409
POST
/api/nsk/v1/booking/segments/{segmentKey}/passengers/{passengerKey}/tickets
Creates a ticket on a passenger segment on the booking in state.
nsk_v1_booking_segments_segmentKey_passengers_passengerKey_tickets_post 2 params body → 201409
PUT
/api/nsk/v1/booking/segments/{segmentKey}/passengers/{passengerKey}/tickets
Updates a ticket on a passenger segment on the booking in state.
nsk_v1_booking_segments_segmentKey_passengers_passengerKey_tickets_put 2 params body → 200500409
PUT
/api/nsk/v1/booking/segments/classOfService/{classModifyKey}
Modifies the class of service for the current booking in state to effect a segment upgrade or downgrade.
nsk_v1_booking_segments_classOfService_classModifyKey_put 1 param body → 200409
GET
/api/nsk/v1/booking/segments/classOfService/availability
Gets class of service availability for the booking in state.
nsk_v1_booking_segments_classOfService_availability_get 4 params → 200404409

Schemas 46

The contract defines 46 schemas that model the data the API accepts and returns. The most detailed are PassengerSegment (29 properties), PassengerFee (16 properties), PassengerTravelDocument (14 properties), PassengerSsr (13 properties). Each schema is shown below with its type and property counts.

TransportationIdentifier
object
Represents the transportation identifier model data.
3 properties 2 required
WeightType
integer
Weight Type enumeration. 0 = Default 1 = Pounds 2 = Kilograms
PassengerInfantCreateRequest
object
Model representing infant data that can be set.
7 properties
InventoryControlType
integer
Defines the different ways inventory is held at the time of sell. 0 = HoldSpace 1 = SoftHoldSpace 2 = ClaimSpace 3 = OversellSpace 4 = StandBy
SsrDurationType
integer
Ssr duration type. 0 = Segment 1 = Journey 2 = Leg
LiftStatus
integer
Lift status enumeration. 0 = Default 1 = CheckedIn 2 = Boarded 3 = NoShow
BaggageStatus
integer
Baggage Status enumeration. 0 = Default 1 = Checked 2 = Removed 3 = Added 4 = AddedPrinted
TicketStatusCode
integer
This enumeration defines the ticket availability status. 0 = Unknown 1 = TicketAvailableForUse 2 = TicketUnavailableForUse 3 = TicketReissueRequiredForPassenge…
TravelClassSeatPreference
integer
Represents a travel class seating preference. 0 = None 1 = Business 2 = Economy 3 = FirstClass
PassengerSeat
object
Model for a passenger seat for a segment.
11 properties
Ticket
object
Model for a ticket applied to a passenger.
5 properties
PassengerSsr
object
The model for a passengers Ssr details.
13 properties
PassengerSegmentBag
object
Model information about the baggage a passenger has on a segment.
6 properties 3 required
IJsonResponseOfPassengerSegment
object
Defines the JSON response contract.
3 properties
Exception
object
4 properties
GssStayType
integer
The type of stay type. 0 = None 1 = Vacation 2 = Business 3 = Duty
SimpleSeatPreference
integer
Represents a simple seating preference. 0 = None 1 = Window 2 = Aisle 3 = Other
MessageStatus
integer
Defines the message status. 0 = General 1 = Warning 2 = Critical
Gender
integer
Defines the different binary gender types. 0 = XX 1 = Male 2 = Female
SeatPreference
object
Represents a single seat preference.
3 properties 2 required
PassengerTravelDocument
object
Model representing a passenger travel document.
14 properties 1 required
SeatInfo
object
The model for the seat information such as deck, seat properties, etc.
3 properties
PassengerBoardingPassDetail
object
Defines information used to populate the printed boarding pass and 2D bar codes.
7 properties
FeeType
integer
Enumeration representing all the different fee types. 0 = All 1 = Tax 2 = TravelFee 3 = ServiceFee 4 = PaymentFee 5 = PenaltyFee 6 = SsrFee 7 = NonFlightServic…
Name
object
Defines a common name.
5 properties
PassengerScore
object
Defines a passenger score.
3 properties 1 required
TicketRequest
object
A ticket request.
4 properties
CollectType
integer
Used to identify the collect type of a service charge. 0 = SellerChargeable 1 = ExternalChargeable 2 = SellerNonChargeable 3 = ExternalNonChargeable 4 = Extern…
PointOfSale
object
Model related to the point of sale. This is for read-only operations.
4 properties
PassengerSegment
object
Model data for the passenger on the booking for the specific segment.
29 properties
SeatPreferences
object
Represents the seating preferences base model.
3 properties
ServiceCharge
object
Model that represents the fare service charge information.
9 properties
TicketIndicatorCode
integer
This enumeration defines the ticket requirements 0 = Unknown 1 = TicketRequired 2 = AutomatedTicketLiftRequired 3 = ManualTicketLiftRequired 4 = AutomatedTicke…
ErrorResponse
object
Defines a unique error response.
8 properties
FeePricingMode
integer
The fee pricing mode enumeration. 0 = MonetaryOnly 1 = PointsOnly
Message
object
Defines a unique informational message.
5 properties
MarketInformation
object
Model information about the market arrival and destination details.
4 properties 4 required
ClassModifyBaseRequest
object
Defines the base class modify request.
4 properties
ClassAvailability
object
Defines a class of service availability for a segment.
6 properties
ChargeType
integer
The type of a service charge. 0 = FarePrice 1 = Discount 2 = IncludedTravelFee 3 = IncludedTax 4 = TravelFee 5 = Tax 6 = ServiceCharge 7 = PromotionDiscount 8…
ClassModify
object
Defines the class modify information.
5 properties
IJsonResponse
object
Defines the JSON response contract for a not content type response.
3 properties
SeatPreferenceStatus
integer
Defines the seat preference status. 0 = Unknown 1 = Met 2 = NotMet
IJsonResponseOfIListOfClassAvailability
object
Defines the JSON response contract.
3 properties
PassengerFee
object
Model representing passenger fee information.
16 properties 1 required
OverbookIndicatorTypes
integer
Specifies the type of code share agreement. 0 = NormalSell 1 = Oversold 2 = ClassOrCabinOversold

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tui-group-booking-segments-api-openapi.yml Raw ↑

Other APIs TUI Group publishes across the network.

TUI Group Account API
TUI Group Airline Profile API
TUI Group Air Shopping API
TUI Group APIS Message API
TUI Group Apo API
TUI Group Auth API
TUI Group Availability API
TUI Group Baggage API
TUI Group Bag Tag API
TUI Group Boarding API
TUI Group Boarding Devices API
TUI Group Booking/addons API
Where this information came from

This is an independent, third-party profile of TUI Group Booking/segments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.