Modifying Air Bookings

An existing Universal Record can be modified to add, update, or delete booked air segment data or cancel air segments through the following child elements of UniversalRecordModifyReq/UniversalModifyCmd:

• AirAdd, which adds a new air segment (PNR) or additional details about an existing air segment to an existing Universal Record.

• AirUpdate, which updates an existing air segment in a Universal Record.

• AirDelete, which deletes air segment data.

This request can also be used to store a price for a booking.

Schema

Located in Universal.xsd:

• UniversalRecordModifyReq
• UniversalRecordModifyRsp

How To

UniversalRecordModifyReq/UniversalModifyCmd is used to modify Universal Record data for traveler information, general UR information, and segment-related data. If multiple modifications are made to a Universal Record, an instance of UniversalModifyCmd must be associated with each change request.

Note: If Routehappy amenities were used in creating the Universal Record, Routehappy amenities return for each flight when modifying a booking to offer customers a detailed view of the amenities for the flights previously selected. N

xPath: UniversalRecordModifyRsp/UniversalRecord/AirReservation/AirPricingInfo/BookingInfo

• /AmenitiesRef

• @IncidentalStops

Adding Air Segments

Note: When adding Segment Data on Apollo (1V), the provider does not have Auto Sort functionality. See Auto Sort for more details.

1. Use the AirAdd child of UniversalModifyCmd to add an air segment or additional details about an existing air segment to an existing Universal Record.

2. Include the required @ReservationLocatorCode to identify the PNR to which the travel segment is added. This ReservationLocatorCode is assigned by the provider and is distinct from the identifier for the UniversalRecord that is issued by Universal API.

3. Include the required BookingTravelerRef to identify the primary traveler for an air segment. This reference is cross-checked with the Reservation Locator Code by Universal API.

4. Add Manual Fares.

5. Add a loyalty card to an existing booking.

   More information

   A single Loyalty Card can be used to accrue points/miles on different carriers (cross-accrual). Up to 10 carriers can be sent in a single LoyaltyCard element in requests to the Galileo (1G) provider.

   Notes:

   • Universal API does not validate the carrier codes against the provider membership mileage table.
   • Universal API does not currently support cross-accrual for multiple airlines on Apollo (1V), or Worldspan (1P) because those providers validate cross-accrual carriers and do not support user entry of cross-accrual carriers.
   • A PNR is not created if the cross-accrual carrier provided does not have a mileage membership agreement with the Loyalty Card carrier. An error is returned: NO CROSS ACCRUAL AGREEMENT EXISTS.

6. Add a seat assignment to an existing booking.

   More information

   Seats can be added to an existing Air Booking that does not already have a seat assignment. If a seat already exists, an error is returned:

   Seat Assignment cannot be processed. Seat is already assigned for mentioned Traveler and FlightSegment. Use AirUpdate to modify the Seat.

   Note: This functionality is available on ACH for easyJet (U2) only. See the Exceptions section for details. Additionally, this functionality is available based on provisioning. Please contact your Support representative for details.

7. Add open segments to an existing reservation.

   More information

   Open segments are air segments that do not specify the flight number. Open segments may or may not include the travel date, and are typically used to secure a fare even though the traveler is not certain of one or more travel dates. Open segments can be booked, modified, and ticketed the same way as regular air segments. Prior to travel, they are exchanged for a ticket with complete flight details.

   The following attributes and values are supported for Open Segments in AirSegment:

   • @OpenSegment="true" (required)

   • @DepartureTime (optional)

     If @DepartureTime is included, it should only include the date and not the time. The time value in @DepartureTime is returned as "T00:00:00.000" in the response.

   • @ArrivalTime (optional)

     If @ArrivalTime is included, it should only include the date and not the time. The time value in @ArrivalTime is returned as “0:00:00” in the response.

   • @FlightTime (optional)

   • @TravelTime (optional)

   • @ClassOfService (optional)

   Regardless of the status that is included in the request to Universal API, open segments are passed to providers as follows:

   • Galileo and Apollo providers are sent Status="NO".
   • Worldspan provider is sent Status="PS".

   Error and Warning Responses

   An error response is returned if:

   • A request with OpenSegment set to "true" includes a FlightNumber value. @FlightNumber is not supported in the request and is not returned in the response.
   • A request is sent without a FlightNumber value and OpenSegment is not set to "true".

8. Store redistributed fares in an existing Universal Record.

   More information

   Private fares can be redistributed (also known as emulation), which allows the requestor to use another Pseudo City Code (PCC). Redistribution requires a prior agreement between the requestor and the other travel provider, such as Selective Access or Group Coding etc. The provider (1G, 1V) establishes the agreement. Many private fares have redistribution coded in Category 15 and 35 to secure the private fare to a requestor and a provider.

   A redistributed fare can be stored in an existing Universal Record. See Storing Redistributed Fares in Existing Universal Records.

9. Add MIRC number to Check form of payment.

   More information

   Credit card form of payment without an associated credit card type (FormOfPayment@Type) is allowed at the PNR level and the stored fare level.

   When the form of payment is "check", the MICR number can be added to an existing check form of payment using the Check@MICRNumber attribute. MICR number is only supported by Apollo.

10. Add Rich Content and Branding details.

    More information

    In all versions, brand information can be added to an existing UR AirAdd/AirPricingInfo/FareInfo/BrandInfo. Alternately, in Universal v34 and higher, Rich Content and Branding details can be added to an existing UR through AirAdd/Brand. See Rich Content and Branding in Air Bookings for details.

11. Add Special Service Requests (SSRs).

    More information

    SSRs apply to air segments only. To add an SSR use AirAdd/SSR with the seat status code in @Status and the SSR code in @Type. Adding SSRs is supported for ACH only on those carriers that allow post-book modifications. If a carrier does not allow post-book modifications, Universal API returns the warning message "Carrier does not support adding SSR." If the specific SSR is not supported by the carrier, the message "SSR type not supported by this carrier" is returned.

12. Restrict or allow flexibility in the fare type.

    More information

    Although optional, returning a value in AirAdd/AirPricingInfo/AirPricingModifiers @FaresIndicator provides the ability to either restrict the type of fare to book or allow flexibility in choosing other fare types.

    The default @FaresIndicator value for Galileo (1G), Apollo (1V), and ACH in all schema versions is PublicAndPrivateFares. In Air.xsd, for Worldspan (1P) only, the default value for @FaresIndicator changed to PublicFaresOnly.

    When booking private fares it is recommended to specify a value for @FaresIndicator. For example, if you are booking a private fare returned in a shop or price response and do not send @FaresIndicator set to PrivateFaresOnly in the book request, if the specified private fare no longer exists, Universal API could book a more expensive public fare. However, if you send FaresIndicator as "PrivateFaresOnly" and the private fare is no longer available, Universal API will return the error "UNABLE TO PRICE".

Ticketing modifiers must be updated using AirUpdate.

Storing a Price

The Store Price procedure includes obtaining a fare quote for a booked itinerary, which is the lowest fare for the booking code, origin/destination, and dates, and then storing the fare quote in the PNR. The Galileo (1G), Apollo (1V), and Worldspan (1P) providers support storing a price.

1. We recommend sending a Universal Record Import or Retrieve first to get the complete PNR details with segments and other information.

2. Send an Air Price request.

   Show required data for repricing

   A Universal Record Import or Retrieve should be sent first to get the complete PNR details with segments and other information.

   When the Air Pricing request includes segment details, the SearchPassenger element, and the 1P AirResrvationLocatorCode (PNR), the existing booking is priced by taking into account the initial booking date and time.

   • AirPriceReq/AirItinerary/AirSegment is used for segment selection and is mandatory.
   • AirPriceReq/SearchPassenger is used for PTC selection and is mandatory.

   • AirPriceReq/AirPricingModifiers@FaresIndicator indicates whether only public fares should be returned or a specific type of private fares.

   • PublicFaresOnly
   • PrivateFaresOnly
   • AgencyPrivateFaresOnly
   • AirlinePrivateFaresOnly
   • PublicAndPrivateFares
   • NetFaresOnly – for pure Private Fares or net fares
   • AllFares – returns public and/or private and/ or net fare or a combination, whichever is cheaper
   • AirPriceReq/AirPricingModifiers@AccountCodeFaresOnly indicates whether or not the private fares returned should be restricted to only those specific to the input account code.
   • AirPriceReq/AirPricingModifiers/AccountCodes/AccountCode is used to get Private Fares and/or net fares with a specific account code.
   • AirPriceReq/AirPricingModifiers@CurrencyType is used for currency override.
   • AirPriceReq/AirPricingModifiers@PlatingCarrier overrides the default plating carrier. Overriding the default carrier can be subject to ADMs.

3. Send the entire AirPricingInfo returned in the response to UniversalRecordModifyReq/UniversalModifyCmd/AirAdd/AirPricingInfo.

With Air v35.0 and later, for 1P only, a value of either NetFaresOnly or AllFares can be sent in the existing @FaresIndicator attribute to specify pricing either for net fares only or for a combination of public, private, and net fares. Two possible scenarios where net fares can be returned in AirPricingModifiers@FaresIndicator are:

• Pure Private and/or Net fares – FaresIndicator as "NetFaresOnly"
• Public and/or private and net fares combinations - FaresIndicator as "AllFares"

With Air v50.0 and later, an enhancement provides the ability to identify and sell city/ticketing city at time of Shop, Price, Book and UR Modify. This helps to identify cross-boarder sales (e.g. price in PAR ticket in NYC) so that fares are accurate throughout a workflow (e.g. shop, price, book, UR Modify). /AirPricingModifiers @SellCity and @TicketingCity can be used together. Release 20.3

This functionality is only supported for Galileo (1G). If sent via 1V, 1P, ACH, the warning message returns, “SellCity and TicketingCity modifier(s) not supported by this provider and have been ignored.” For example:
<AirPricingInfo ProviderCode="1G" Key="s8+gKLBAAA/B7eWQAAAAAA==" ApproximateTaxes="COP41300" Taxes="COP41300" EquivalentBasePrice="COP249000" ApproximateBasePrice="COP249000" ApproximateTotalPrice="COP290300" BasePrice="USD61.00" TotalPrice="COP290300"
PlatingCarrier="AA" ETicketability="Yes" IncludesVAT="false" PricingMethod="Guaranteed" LatestTicketingTime="2020-06-24T23:59:00.000-05:00">
...
<AirPricingModifiers TicketingCity="PAR" SellCity="NYC"/>


 

Updating Air Segments

Notes: 

• ACH does not support AirUpdate.

• When updating Segment Data on Apollo (1V), the provider does not have Auto Sort functionality. See Auto Sort for more details.

1. Use the AirUpdate child of UniversalModifyCmd to modify an existing air segment in a Universal Record.

2. Ensure ReservationLocatorCode and BookingTravelerRef are included in the request to identify the PNR. 

Modify the seat assignment in an existing booking.

Seats can be modified in an existing Air Booking that already has a seat assignment. If a modification request is sent and the booking does not already have a seat, an error is returned:

No seat assignment exists to modify for mentioned Traveler and FlightSegment. Use AirAdd to add new seat assignments.

Note: This functionality is available on ACH for easyJet (u2) only. See the Exceptions section for details. Additionally, this functionality is available based on provisioning. Please contact your Support representative for details.

Update SSRs and OSIs.

Note: SSRs and OSIs cannot be modified through AirUpdate.

SSRs apply to air segments only. To update an SSR or OSI, it must be deleted using the 'SSR' or 'OSI' enumeration of the AirDelete/Element attribute and then recreated using AirAdd.

Update Ticketing Modifiers.

Only existing ticketing modifiers can be updated. For example, a user has commission, endorsement and plating carrier as UA. The user can change the plating carrier (or any other Ticketing Modifier) from UA to DL, if necessary.

Change the Class of Service.

A class of service for an air segment can be modified if the new class of service for the requested air segment is available.

Responses may vary. If AirUpdate contains a request for:

• Different air segments for both Segment Status and Class of Service within the PNR (Provider Reservation), then the Class of Service is updated before the Segment Status is updated for the segment.
• The same air segment for both Segment Status and Class of Service within the PNR:
• Universal API ignores the change of Segment Status and only performs the change of Class of Service.
• If the requested Class of Service is the same (or NULL) as in the Universal Record, the Class of Service is not updated.
• If the requested Segment Status is different from the Segment Status in the Universal Record, a warning is returned: Segment Status change ignored for segments undergoing class of service update.

If the PNR has changed, a warning is returned to advise the user to re-price the segment/connection: The reservation returned by the host changed. The segment information is now updated and the pricing data has been removed.

Change the Date or Time.

The date or time of an air segment can be modified. When multiple values are changed in a single AirUpdate request, the following rules of precedence apply:

• Date and class of service can be changed in a single request.

• If the date is changed:
• A change in status is ignored.
• A change in time is ignored.

• If the date or time is changed, a change in flight number is ignored.

  Note: Use UniversalRecordModify/AirAdd and /AirCancel rather than AirUpdate to change flights.

• If status is changed, a change in time is ignored.
• If the class of service is changed, a change in time is ignored.

Change the Status.

To change the status of one or more segments, use /AirUpdate/AirSegment/Status. Note:

• If the date is changed, any change in status is ignored.
• If status is changed, a change in time is ignored.

Manually adjust the fare.

Manual fare adjustment functionality allows increases or decreases to be applied to a fare quote when the appropriate parameters are set in Shop/Price/Book requests. The fare can be increased or decreased either by percentage or flat amount. The user can increase or decrease either the base amount or total.

This functionality is available for Galileo, Apollo, and Worldspan.

See Manual Fare Adjustments for details.

Modify Seats.

Universal v44.0 and later allows you to save existing seats when adding new seats. This functionality allows you to processes a seat update in a session flow, so that the PNR is saved and End-Transacted if the new seat is successfully added. Contact your Travelport representative for more information about accessing this functionality. Release 18.1

Notes:

• If any Seat Selection fails then an Ignore is generated. Only if all the seat selections are successful will an ET be generated.
• A seat change is saved even when the Status Code is not the same as the original seat. For Example, if the original seat status code is HK and the new seat is UC, Universal API proceeds and End Transacts.
• Universal API does not validate nor restrict the combination of seat change with other updates to the Universal Record. It is recommended that the end user does not combine with other changes as it can result in SIMULTANEOUS CHANGE ERROR.

• The xPath is UniversalRecordModify/UniversalModifyCmd/AirUpdate/SpecificSeatAssignment or /AirUpdate/AutoSeatAssignment

Add a credit card authorization.

You can add a credit card authorization to a Universal Record using the Universal Record Modify request (UniversalModifyCmd/AirAdd/CreditCardAuth). The following sample shows how to add a credit card authorization.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Body>
    <univ:UniversalRecordModifyReq AuthorizedBy="Test" TargetBranch="ABC123" Version="0" ReturnRecord="true" xmlns:univ="http://www.travelport.com/schema/universal_v44_0" xmlns:com="http://www.travelport.com/schema/common_v44_0" xmlns:air="http://www.travelport.com/schema/air_v44_0" xmlns:pas="http://www.travelport.com/schema/passive_v44_0" TraceId="5c185bc4-ab9a-4d45-ba61-2fde8a91bd94">
      <com:BillingPointOfSaleInfo OriginApplication="uAPI"/>
      <univ:RecordIdentifier UniversalLocatorCode="DZZ10Z" ProviderCode="1G" ProviderLocatorCode="123ABC"/>
      <univ:UniversalModifyCmd Key="muGdyDGLRz6H6/gRNTVbqA==">
        <univ:AirAdd ReservationLocatorCode="DVVVVV">
          <com:CreditCardAuth PaymentRef="DeTim74JSCOAzDdWmoAuxw==" Amount="AUD892.60" AuthCode="7854" AuthResultCode="Approved" AVSResultCode="123"/>
        </univ:AirAdd>
      </univ:UniversalModifyCmd>
    </univ:UniversalRecordModifyReq>
  </soapenv:Body>
</soapenv:Envelope>

Modify the Form of Payment.

When the form of payment is check, the MICR number of a check form of payment can be updated using the Check@MICRNumber attribute.

If the MICR number is different in the UR Modify request than in the existing Universal Record, the MICR number is updated. MICR number is only supported by Apollo.

Notes: 

• Pricing attributes are not shown in the Air Pricing Solution when the price changes.
• If a discontinuous Air Segment is added to a Universal Record using AirUpdate, a Continuity Check error is returned: Segment continuity validation failed.

Deleting Air Segment Data

1. Use the AirDelete child of UniversalModifyCmd to delete existing data from an air segment or to delete an entire air segment from an existing Universal Record.

Notes:

• See Canceling Travel Segments via the UR for more information on deleting entire air segments from an existing Universal Record.

• When deleting Segment Data on Apollo (1V), the provider does not have Auto Sort functionality. See Auto Sort for more details.
2. Enter required data:
   • The ReservationLocatorCode attribute identifies the PNR with the associated air segments.
   • The Element attribute indicates the type of data to be deleted.
     • If Element is set to "AirSegment", the entire air segment is canceled. See Canceling Travel Segments via the UR for more information on deleting entire air segments from an existing Universal Record.
     • Because the Element attribute is shared by several segment types, not all enumerations are used by air segments.
   • A Key from the PNR uniquely identifies the specific item to be deleted based on the unique key assigned to that item.
   • The BookingTravelerRef identifies the primary traveler for an air segment. This reference is cross-checked with the Reservation Locator Code by Universal API.

Notes:

• To delete the MICR number for a check form of payment, use AirUpdate and send a blank MICRNumber attribute. MICR number is only supported by Apollo.
• When dual SSRs exist, an ASVC SSR cannot be deleted. Instead, the standard SSR should be deleted. If Air Delete is sent and @Element="SSR", Universal API checks the Universal Record to determine if the SSR being deleted is an ASVC SSR. If it is, Universal API checks if there are dual SSRs, and if dual SSRs exist, an error is returned.
Show Standard and ASVC SSRs

Standard SSR

<common_v42_0:SSR Key="+De1MpZ0RZe4CWCcg+x9/g==" SegmentRef="8GnCauH0Rly7X2wGpJUm3g==" Status="NN" Type="XBAG" FreeText="XBAG" Carrier="A3" ProviderReservationInfoRef="LjSbJKZpR822wH22hiJE0A==" ElStat="A" />

ASVC SSR

<common_v42_0:SSR Key="C/9h5zt/TDWLs5JY+zxFtw==" SegmentRef="8GnCauH0Rly7X2wGpJUm3g==" Status="NN" Type="ASVC" FreeText="**C/0AA/XBAG/EXCESS BAGGAGE" Carrier="A3" ProviderReservationInfoRef="LjSbJKZpR822wH22hiJE0A==" ElStat="A" />

• ASVC SSRs for paid seats cannot be deleted. Universal API validates the SSR code in the ASVC SSR FreeText to determine if it is a paid seat SSR. If so, Universal API does not send the request to delete the ASVC SSR.

Show codes

• SEAT
• RQST
• NSST
• NSSA
• NSSW
• NSSB
• SMSA
• SMSW
• SMSB
• SMST

If other deletions were successful, a warning message is returned in UniversalRecordModifyRsp. If no deletions were successful, an error is returned. The error/warning message is the same:

ASVC delete not allowed - delete assigned seat.

If the SSR code in the ASVC SSR FreeText is not a paid seat SSR and does not have a dual SSR, Universal API deletes the non-paid seat ASVC SSR.

Auto Sort, Travel Order, and Provider Segment Order

Universal API builds segment reorder request based on the TravelOrder attribute while modifying the PNR when the segments not in Chronological order.

Galileo (1G)

Galileo has auto sort (ASP) setting on the Agency Action Table (AAT), which, when enabled, allows the agent to enter segments in any order and the provider reorders the segments to automatically be in chronological order. Thus, when Universal API, on Galileo, adds a segment to an existing PNR, the new segment is added to the bottom of the itinerary, and the provider puts it into the correct chronological order. However, when ASP is turned off on AAT, automatic re-ordering doesn't place.

Apollo (1V)

On Apollo, the ASP setting does not exist, and thus segments are never re-ordered. This may create confusion when modifying or deleting segments. Following are examples of the Apollo provider responses where TravelOrder and ProviderSegmentOrder are highlighted to demonstrate possible complications.

1V – PNR – Not in chronological order

Request

NMQZVE/85 XDBKR C737685 AG 10559146 16DEC

1.1WHIT/STE

1 . AA 1736 O 14JAN CLTBDL HK1 734A 930A * E TU

2. CCR ZI HK1 BDL 14JAN-15JAN ECAR

/PUP-BDLT01/RQ-USD30.00DY-UNL FM XH 22.51 UNL FM/BS-10559146/ARR

-0930-AA 1736/RC-IJ/DT-0930/NM-WHIT STE/CF-34705681US3*

3. HHL MC HK 1 HFD 14JAN-15JAN 1NT 39855 MARRIOTT HARTFORDWI

1 A00REGA -1 /RG-USD209.00/AGT10559146/G-VI4XXXXXXXXXXX5111EXP1128

/NM-WHIT STE/CF-30041914*

4 . UA 1304 N 16JAN BDLORD HK1 605A 752A * E TH

5. HHL XV HK 1 CHI 14JAN-16JAN 2NT 26048 SPRINGHILL STES ELM

1 A00SM3A -1 /RG-USD107.10/AGT10559146/NM-WHIT STE/G-DPSTVI4XXXXXX

XXXXX5111EXP1128/CF-30041924*

 

Response

TravelOrder is 1, 5, 3, 4, 2, whereas ProviderSegmentOrder is 1, 4, 3, 5, 2.

<air:AirSegment Key="kRD37OUqWDK==" Group="0" Carrier="AA" CabinClass="Economy" FlightNumber="1736" 
ProviderCode="1V" Origin="CLT" Destination="" TravelOrder="1" ProviderSegmentOrder="1" > 

<air:AirSegment Key="kRD37OUqWDKA8k76A==" Group="1" Carrier="UA" CabinClass="Economy" FlightNumber="1304" 
ProviderCode="1V" Origin="BDL" Destination=""TravelOrder="5" ProviderSegmentOrder="4" > 

<hotel:HotelReservation  BookingConfirmation="30041914" LocatorCode="01Q0LWVK" 
CreateDate="2024-12-16T07:52:50.873+00:00" ModifiedDate="2" TravelOrder="3" ProviderSegmentOrder="3"> 

<hotel:HotelReservation BookingConfirmation="30041924" LocatorCode="01Q0LYQX" 
ProviderReservationInfoRef="kRD37OUqWDKAzk76FAAAAA==" TravelOrder="4" ProviderSegmentOrder="5"> 

<vehicle:VehicleReservation  SupplierCode="ZI" BookingConfirmation="34705681US3" LocatorCode="01Q0M19W" 
Status="HK" TravelOrder="2" ProviderSegmentOrder="2"> 

UR Modify: Delete Accounting remarks from the Existing PNR

Request

When the segment number order on the provider system is 1, 2, 3, 5, 4, the delete response returns the TravelOrder and ProviderSegmentOrder return the matching order in 1, 5, 3, 4, 2

NMQZVE/85 XDBKR C737685 AG 10559146 16DEC

1.1WHIT/STE

1 . AA 1736 O 14JAN CLTBDL HK1 734A 930A * E TU

2. CCR ZI HK1 BDL 14JAN-15JAN ECAR

/PUP-BDLT01/RQ-USD30.00DY-UNL FM XH 22.51 UNL FM/BS-10559146/ARR

-0930-AA 1736/RC-IJ/DT-0930/NM-WHIT STE/CF-34705681US3*

3. HHL MC HK 1 HFD 14JAN-15JAN 1NT 39855 MARRIOTT HARTFORDWI

1 A00REGA -1 /RG-USD209.00/AGT10559146/G-VI4XXXXXXXXXXX5111EXP1128

/NM-WHIT STE/CF-30041914*

4. HHL XV HK 1 CHI 14JAN-16JAN 2NT 26048 SPRINGHILL STES ELM

1 A00SM3A -1 /RG-USD107.10/AGT10559146/NM-WHIT STE/G-DPSTVI4XXXXXX

XXXXX5111EXP1128/CF-30041924*

5 . UA 1304 N 16JAN BDLORD HK1 605A 752A * E TH

Response

<air:AirSegment Key="kRD37OUqWDKA6k76FAAAAA==" Group="0" Carrier="AA" CabinClass="Economy" 
FlightNumber="1736" ProviderCode="1V" Origin="CLT" Destination="BDL"  TravelOrder="1" 
ProviderSegmentOrder="1" >

<air:AirSegment Key="kRD37OUqWDKA8k76FAAAAA==" Group="1" Carrier="UA" CabinClass="Economy" 
FlightNumber="1304" ProviderCode="1V" Origin="BDL" Destination="ORD"  TravelOrder="5" 
ProviderSegmentOrder="5" >

<hotel:HotelReservation BookingConfirmation="30041914" LocatorCode="01Q0LWVK" 
CreateDate="2024-12-16T07:52:50.873+00:00"  TravelOrder="3" ProviderSegmentOrder="3">

<hotel:HotelReservation  BookingConfirmation="30041924" LocatorCode="01Q0LYQX" 
ProviderReservationInfoRef="kRD37OUqWDKAzk76FAAAAA==" TravelOrder="4" ProviderSegmentOrder="4">

<vehicle:VehicleReservation  BookingConfirmation="34705681US3" LocatorCode="01Q0M19W" 
TravelOrder="2" ProviderSegmentOrder="2">

This functionality is working as designed. Ensure you develop your application to consider the TravelOrder and ProviderSegmentOrder when using Apollo (1V) as your provider.

Exceptions