Deprecated Features in release 1.4.0¶
Changes in schemas that may affect the current functionality.
We do our best to develop our product and to do it simple and clear, that’s why we would like to inform you that for the February 2025 we plan the release 1.4.0. It will contain changes which may influence backward compatibility and may cause significant changes in the processes of tickets and extra services booking and issuing.
We kindly ask you to get acquainted with the planned changes and to plan the necessary revisions on your side for smooth switch to use of the version 1.4.0.
In case of any questions please feel free to contact us via the mailbox support@mixvel.com
General changes¶
New logic for displaying baggage and carry-on luggage¶
In the MixVel.Gate 1.3.7 release a new logic for displaying baggage and carry-on luggage norms was added in the BaggageAllowance structures of all response messages. The previous logic will be supported until the 1.4.0 Deprecated Features release.
The elements WeightAllowance and DimensionAllowance will be removed from the response messages AirShoppingRS, OfferPriceRS, OrderViewRS, OrderReshopRS in the 1.4.0 release:
- …/Response/DataLists/BaggageAllowanceList/BaggageAllowance/WeightAllowance
- …/Response/DataLists/BaggageAllowanceList/BaggageAllowance/DimensionAllowance
These elements are replaced by the Allowed and Excluded elements, which include all Weight and Dimension options, as well as Name and LimitValue:
- …/Response/DataLists/BaggageAllowanceList/BaggageAllowance/Allowed
- …/Response/DataLists/BaggageAllowanceList/BaggageAllowance/Excluded
Example of the structure <BaggageAllowance> after the release 1.3.7:
<BaggageAllowance>
<BaggageAllowanceID>93052587-7bf0-4c01-9310-f711d216f5c8</BaggageAllowanceID>
<DescText>PC</DescText>
<PieceAllowance>
<TotalQty>1</TotalQty>
</PieceAllowance>
<TypeCode>Checked</TypeCode>
<Allowed>
<Name>SPORTING EQUIPMENT 23KG (053)</Name>
<LimitValue>1</LimitValue>
<WeightAllowance>
<MaximumWeightMeasure UnitCode="Kilogram">23</MaximumWeightMeasure>
</WeightAllowance>
</Allowed>
<Allowed>
<Name>UPTO50LB 23KG AND80LI 203LCM (0GP)</Name>
<LimitValue>1</LimitValue>
<DimensionAllowance>
<BaggageDimensionCategory>Total</BaggageDimensionCategory>
<MaxMeasure UnitCode="Inch">80</MaxMeasure>
</DimensionAllowance>
<DimensionAllowance>
<BaggageDimensionCategory>Total</BaggageDimensionCategory>
<MaxMeasure UnitCode="Centimetre">203</MaxMeasure>
</DimensionAllowance>
<WeightAllowance>
<MaximumWeightMeasure UnitCode="Kilogram">23</MaximumWeightMeasure>
</WeightAllowance>
<WeightAllowance>
<MaximumWeightMeasure UnitCode="Pound">50</MaximumWeightMeasure>
</WeightAllowance>
</Allowed>
<Allowed>
<Name>SPORT FIREARMS UP TO 50LB 23KG (0HW)</Name>
<LimitValue>1</LimitValue>
<WeightAllowance>
<MaximumWeightMeasure UnitCode="Kilogram">23</MaximumWeightMeasure>
</WeightAllowance>
<WeightAllowance>
<MaximumWeightMeasure UnitCode="Pound">50</MaximumWeightMeasure>
</WeightAllowance>
</Allowed>
<Excluded>
<Name>STROLLER OR PUSHCHAIR (0F4)</Name>
</Excluded>
<Excluded>
<Name>WHEELCHAIR (0GM)</Name>
</Excluded>
<Excluded>
<Name>ADD FREE BAG TAG (0JX)</Name>
</Excluded>
</BaggageAllowance>
Description of the elements of the structure <BaggageAllowance>
- Allowed
Description: It contains a list of all possible options, which are available for carriage under the given baggage allowance and type.
A new parameter: It includes a <LimitValue> parameter, which is responsible for the maximum number of one type of the baggage.
Example:
<Allowed>
<Name>UPTO 22LB 10KG AND45LI 115LCM (0E3)</Name>
<LimitValue>1</LimitValue>
</Allowed>
- Excluded
Description: It contains a list of all unavailable options for carriage under the given baggage allowance and type.
- LimitValue
Description: The number that indicates the maximum amount of this type of baggage or carry-on luggage according to these rules.
Note: If PieceAllowance/TotalQty = 2, then no more than 2 pieces of baggage can be taken. If <LimitValue> = 1 - then 1 piece of baggage is available only. If <LimitValue> = 2 - no more than 2 pieces.
- CommentText
Description: It contains comments that are listed in the baggage or carry-on luggage allowance file.
Example:
<CommentText>1 STROLLER WILL BE CARRIED FREE IN ADDITION TO FREE BAGGAGE ALLOWANCE</CommentText>
Error transmission structures¶
- CanRetry
Description: The <CanRetry> parameter displays whether the message can be resent.
Status: This parameter becomes optional and will only be returned in cases of network availability issues, when retrying the request might lead to a successful result.
- RetryAfter
Description: If <CanRetry> = true, it indicates the recommended number of seconds after which the request should be resent.
Example of the error structure:
The message in <DescText> implies that a repeat request is recommended after a specified time interval:
<Error>
<ErrorType>InternalServerError</ErrorType>
<CanRetry>true</CanRetry>
<RetryAfter>60</RetryAfter>
<Code>MIX-201999</Code>
<DescText>Сервис временно недоступен. Повторите попытку через 60 секунд</DescText>
</Error>
Changes in methods¶
Request for commercial offer¶
Endpoint: /api/Order/AirShopping
Specifying the date in the request¶
The DateRangeStart and DateRangeEnd elements are being removed:
-
Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/DateRangeStart
-
Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/DateRangeEnd
The new Date element is going to be used instead:
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/Date.
The Date element will be added to the query schema in release 1.3.8. The removed DateRangeStart and DateRangeEnd elements will be supported until the 1.4.0 Deprecated Features release.
Show the example of Mixvel_AirShoppingRQ request on this page
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body>
<MessageInfo MessageId="69b4b0e6-8b3f-4c21-a329-efbeab19c7ff" TimeSent="2024-11-15T16:13:55Z"/>
<AppData>
<shop:Mixvel_AirShoppingRQ xmlns:shop="https://www.mixvel.com/API/XSD/Mixvel_AirShoppingRQ/1_01">
<Request>
<FlightRequest>
<FlightRequestOriginDestinationsCriteria>
<OriginDestCriteria>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
<PrefLevel>
<PrefLevelCode>Required</PrefLevelCode>
</PrefLevel>
</CabinType>
<DestArrivalCriteria>
<IATA_LocationCode>LED</IATA_LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2024-12-01</Date>
<IATA_LocationCode>MOW</IATA_LocationCode>
</OriginDepCriteria>
</OriginDestCriteria>
</FlightRequestOriginDestinationsCriteria>
</FlightRequest>
<Paxs>
<Pax>
<PaxID>Pax-1</PaxID>
<PTC>ADT</PTC>
</Pax>
</Paxs>
</Request>
</shop:Mixvel_AirShoppingRQ>
</AppData>
</Body>
</MixEnv:Envelope>
Filter by Booking Subclass¶
The <MixRBDInd> parameter, that is used to enable/disable the combination of subclasses, is transferred in the FlightCriteria filter structure. Until release 1.4.0 the structure is supported:
- Mixvel_AirShoppingRQ/Request/ShoppingCriteria/FlightCriteria/RBD/MixRBDInd
Current structure, starting with release 1.3.7:
- Mixvel_AirShoppingRQ/Request/ShoppingCriteria/FlightCriteria/MixRBDInd
The following elements become mandatory:
-
.../ShoppingCriteria/FlightCriteria/RBD/RBD_Code
-
.../ShoppingCriteria/FlightCriteria/MixRBDInd
The subclass code element becomes optional:
- .../ShoppingCriteria/FlightCriteria/RBD
An example of a correct structure without linking a subclass to a segment:
<FlightCriteria>
<MixRBDInd>true</MixRBDInd>
<RBD>
<RBD_Code>L</RBD_Code>
<RBD_Code>O</RBD_Code>
</RBD>
</FlightCriteria>
An example of an actual structure with subclass binding to segments:
Show the example of Mixvel_AirShoppingRQ request on this page
<envelope:Envelope xmlns:envelope="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header></Header>
<Body>
<MessageInfo MessageId="941d89b8-323b-4fdd-895d-b4dfa560ef1f" TimeSent="2024-11-07T16:04:38Z"></MessageInfo>
<AppData>
<shop:Mixvel_AirShoppingRQ xmlns:shop="https://www.mixvel.com/API/XSD/Mixvel_AirShoppingRQ/1_01">
<Request xmlns="">
<FlightRequest>
<FlightRequestOriginDestinationsCriteria>
<OriginDestCriteria>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
<PrefLevel>
<PrefLevelCode>Required</PrefLevelCode>
</PrefLevel>
</CabinType>
<DestArrivalCriteria>
<IATA_LocationCode>LED</IATA_LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2024-12-01</Date>
<IATA_LocationCode>MOW</IATA_LocationCode>
</OriginDepCriteria>
<OriginDestID>Origin-Dest-1</OriginDestID>
</OriginDestCriteria>
<OriginDestCriteria>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
<PrefLevel>
<PrefLevelCode>Required</PrefLevelCode>
</PrefLevel>
</CabinType>
<DestArrivalCriteria>
<IATA_LocationCode>MOW</IATA_LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2024-12-11</Date>
<IATA_LocationCode>LED</IATA_LocationCode>
</OriginDepCriteria>
<OriginDestID>Origin-Dest-2</OriginDestID>
</OriginDestCriteria>
</FlightRequestOriginDestinationsCriteria>
</FlightRequest>
<Paxs>
<Pax>
<PaxID>Pax-1</PaxID>
<PTC>ADT</PTC>
</Pax>
</Paxs>
<ShoppingCriteria>
<FlightCriteria>
<MixRBDInd>true</MixRBDInd>
<RBD>
<OriginDestRefID>Origin-Dest-1</OriginDestRefID>
<RBD_Code>Y</RBD_Code>
</RBD>
<RBD>
<OriginDestRefID>Origin-Dest-2</OriginDestRefID>
<RBD_Code>N</RBD_Code>
</RBD>
</FlightCriteria>
</ShoppingCriteria>
</Request>
</shop:Mixvel_AirShoppingRQ>
</AppData>
</Body>
</envelope:Envelope>
Filter by departure/arrival time range¶
Unused elements are being removed in the Mixvel_AirShoppingRQ request:
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/Time
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/TimeBeforeDuration
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/TimeAfterDuration
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/DestArrivalCriteria/Time
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/DestArrivalCriteria/TimeBeforeDuration
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/DestArrivalCriteria/TimeAfterDuration
The ability to choose the time range for departure and arrival (in local time) in the search request for commercial offers is done through the following elements:
Departure time range:
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/TimeRangeStart
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/OriginDepCriteria/TimeRangeEnd
Arrival time range:
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/DestArrivalCriteria/TimeRangeStart
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/DestArrivalCriteria/TimeRangeEnd
Example of specifying a range of arrival time in Mixvel_AirShoppingRQ:
<DestArrivalCriteria>
<IATA_LocationCode>LED</IATA_LocationCode>
<TimeRangeStart>09:00:00</TimeRangeStart>
<TimeRangeEnd>13:00:00</TimeRangeEnd>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2024-11-30</Date>
<IATA_LocationCode>MOW</IATA_LocationCode>
</OriginDepCriteria>
Deleting the CacheSettings array¶
The unused array CacheSettings in Mixvel_AirShoppingRQ is going to be deleted:
- Mixvel_AirShoppingRQ/Request/ResponseParameters/CacheSettings
Deleting the ProfileConsentInd element¶
The ProfileConsentInd element is going to be deleted from the Mixvel_AirShoppingRQ and Mixvel_OrderChangeRQ requests schemes, and from the Mixvel_SeatAvailabilityRS response message:
- Mixvel_AirShoppingRQ/Request/Paxs/Pax/ProfileConsentInd
- Mixvel_OrderChangeRQ/Request/DataLists/PaxList/Pax/ProfileConsentInd
- Mixvel_SeatAvailabilityRS/Response/DataLists/PaxList/Pax/ProfileConsentInd
Deleting the AllowConnectionsInd element in the CalendarDateCriteria structure¶
The AllowConnectionsInd is going to be deleted from the Mixvel_AirShoppingRQ when the calendar is requested:
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/CalendarDateCriteria/AllowConnectionsInd
Instead, the AllowDirectInd element is added, that is responsible for displaying direct flights only:
- Mixvel_AirShoppingRQ/Request/FlightRequest/FlightRequestOriginDestinationsCriteria/OriginDestCriteria/CalendarDateCriteria/AllowDirectInd
Example of a correct Mixvel_AirShoppingRQ request to get the best prices in a date range:
Show the example of Mixvel_AirShoppingRQ request on this page
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body>
<MessageInfo MessageId="69b4b0e6-8b3f-4c21-a329-efbeab19c7ff" TimeSent="2024-11-15T16:13:55Z"/>
<AppData>
<shop:Mixvel_AirShoppingRQ xmlns:shop="https://www.mixvel.com/API/XSD/Mixvel_AirShoppingRQ/1_01">
<Request>
<FlightRequest>
<FlightRequestOriginDestinationsCriteria>
<OriginDestCriteria>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
<PrefLevel>
<PrefLevelCode>Required</PrefLevelCode>
</PrefLevel>
</CabinType>
<CalendarDateCriteria>
<DaysAfterNumber>3</DaysAfterNumber>
<DaysBeforeNumber>3</DaysBeforeNumber>
<AllowDirectInd>true</AllowDirectInd>
</CalendarDateCriteria>
<DestArrivalCriteria>
<IATA_LocationCode>SVX</IATA_LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2024-12-25</Date>
<IATA_LocationCode>KGD</IATA_LocationCode>
</OriginDepCriteria>
</OriginDestCriteria>
<OriginDestCriteria>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
<PrefLevel>
<PrefLevelCode>Required</PrefLevelCode>
</PrefLevel>
</CabinType>
<CalendarDateCriteria>
<DaysAfterNumber>3</DaysAfterNumber>
<DaysBeforeNumber>3</DaysBeforeNumber>
<AllowDirectInd>true</AllowDirectInd>
</CalendarDateCriteria>
<DestArrivalCriteria>
<IATA_LocationCode>KGD</IATA_LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2025-01-10</Date>
<IATA_LocationCode>SVX</IATA_LocationCode>
</OriginDepCriteria>
</OriginDestCriteria>
</FlightRequestOriginDestinationsCriteria>
</FlightRequest>
<Paxs>
<Pax>
<PaxID>1</PaxID>
<PTC>ADT</PTC>
</Pax>
</Paxs>
</Request>
</shop:Mixvel_AirShoppingRQ>
</AppData>
</Body>
</MixEnv:Envelope>
Deleting AircraftScheduledDateTime and Mileage elements¶
AircraftScheduledDateTime element is going to be replaced by ScheduledDateTime:
- …/Response/DataLists/PaxSegmentList/Paxsegment/Arrival/ScheduledDateTime
Mileage element is going to be replaced by Distance:
- …/Response/DataLists/PaxSegmentList/Paxsegment/Distance
Example of displaying parameters AircraftScheduledDateTime and Mileage in Mixvel_AirShoppingRS:
Show the example of segment information on this page
<PaxSegmentList>
<PaxSegment>
<Arrival>
<ScheduledDateTime>2024-10-22T20:00:00</ScheduledDateTime>
<IATA_LocationCode>LED</IATA_LocationCode>
<StationName>Санкт-Петербург(Пулково)</StationName>
<TerminalName>1</TerminalName>
</Arrival>
<DatedOperatingLeg>
<Arrival>
<ScheduledDateTime >2024-10-22T20:00:00</ ScheduledDateTime >
<IATA_LocationCode>LED</IATA_LocationCode>
<StationName>Санкт-Петербург(Пулково)</StationName>
<TerminalName>1</TerminalName>
</Arrival>
<CarrierAircraftType>
<CarrierAircraftTypeCode>SU9</CarrierAircraftTypeCode>
</CarrierAircraftType>
<DatedOperatingLegID>74b4fbb9-90ba-440a-a452-b9b1ba645c95</DatedOperatingLegID>
<Dep>
<ScheduledDateTime >2024-10-22T18:30:00</ ScheduledDateTime >
<IATA_LocationCode>VKO</IATA_LocationCode>
<StationName>Москва(Внуково)</StationName>
<TerminalName>A</TerminalName>
</Dep>
</DatedOperatingLeg>
<Dep>
<ScheduledDateTime>2024-10-22T18:30:00</ScheduledDateTime>
<IATA_LocationCode>VKO</IATA_LocationCode>
<StationName>Москва(Внуково)</StationName>
<TerminalName>A</TerminalName>
</Dep>
<Duration>PT1H30M</Duration>
<Distance UnitCode="Mileage">390</Distance>
<FranchiseCarrierInfo>
<CarrierDesigCode>FV</CarrierDesigCode>
<FranchiseCarrierFlightNumberText>6176</FranchiseCarrierFlightNumberText>
</FranchiseCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>SU</CarrierDesigCode>
<MarketingCarrierFlightNumberText>6176</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
<SegmentType>Aircraft</SegmentType>
<PaxSegmentID>1bf15397-890c-4d5c-9879-83382f88c7da</PaxSegmentID>
</PaxSegment>
</PaxSegmentList>
Deleting CarrierAircraftType structure¶
In release 1.4.0 CarrierAircraftTypeCode and CarrierAircraftTypeName elements are removed from response messages. The change affects all methods.
-
…/Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/CarrierAircraftType/CarrierAircraftTypeCode
-
.../Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/CarrierAircraftType/CarrierAircraftTypeName
The CarrierAircraftType element is replaced by CarrierType.
The CarrierAircraftTypeCode and CarrierAircraftTypeName elements are replaced by the CarrierTypeCode and CarrierTypeName elements, respectively.
The CarrierAircraftTypeCode element is replaced with CarrierTypeCode: …/Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/CarrierType/CarrierTypeCode
The CarrierAircraftTypeName element is replaced with CarrierTypeName: …/Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/CarrierType/CarrierTypeName
Changing the necessity of FranchiseCarrierInfo elements in Mixvel_AirShoppingRS¶
The mandatory display of elements in FranchiseCarrierInfo is changed:
The FranchiseCarrierFlightNumberText element becomes optional in Mixvel_AirShoppingRS:
- Mixvel_AirShoppingRS/Response/DataLists/PaxSegmentList/PaxSegment/FranchiseCarrierInfo/FranchiseCarrierFlightNumberText
The CarrierDesignCode element becomes mandatory in Mixvel_AirShoppingRS: - Mixvel_AirShoppingRS/Response/DataLists/PaxSegmentList/PaxSegment/FranchiseCarrierInfo/CarrierDesignCode
Deleting OffersGroup structure¶
Methods affected: Mixvel_AirShoppingRS, Mixvel_AvailabilityRS
The OffersGroup structure and the CarrierOffers element it contains are deleted. Information will be posted in Offer for AirShoppingRS and Offers for AvailabilityRS.
- Mixvel_AirShoppingRS/Response/Offer
- Mixvel_AvailabilityRS/Response/Offers
Deleting the RichContentList structure¶
Methods affected: Mixvel_AirShoppingRS / Mixvel_AvailabilityRS / Mixvel_OfferPriceRS
The RichContentList structure, which contains the Amenities content from Routehappy, is going to be deleted. Instead, a RichContent structure with the same content will be added:
- Mixvel_AirShoppingRS/Response/DataLists/RichContent
- Mixvel_AvailabilityRS/Response/DataLists/RichContent
- Mixvel_OfferPriceRS/Response/DataLists/RichContent
Request for offer update Mixvel_OfferPriceRQ¶
Endpoint: /api/Order/OfferPrice
Changing the necessity of PricedOffer element¶
The PricedOffer element containing the refined information on the commercial offer, which is sent for actualization, becomes optional in the Mixvel_OfferPriceRS:
Mixvel_OfferPriceRS/Response/PricedOffer
Deleting the OfferItemRefID structure from the SelectedOfferItem¶
The structure SelectedOfferItem/OfferItemRefID is going to be deleted from the Mixvel_OfferPriceRQ/Request/PricedOffer/SelectedOffer. Only the OfferRefID must be passed in the OfferPriceRQ request.
Example of a correct OfferPriceRQ request:
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body>
<MessageInfo MessageId="79b67a26-6fc3-41e3-8ac4-14e0ac0245c8" TimeSent="2021-03-17T17:37:47Z"/>
<AppData>
<shop:Mixvel_OfferPriceRQ xmlns:shop="https://www.mixvel.com/API/XSD/Mixvel_OfferPriceRQ/1_00">
<Request>
<PricedOffer>
<SelectedOffer>
<OfferRefID>1b6e89ac-d1ce-418f-8f05-7592769d1fc3</OfferRefID>
</SelectedOffer>
</PricedOffer>
</Request>
</shop:Mixvel_OfferPriceRQ>
</AppData>
</Body>
</MixEnv:Envelope>
Name and ServiceCategory elements of additional services¶
Methods affected: Mixvel_ServiceListRS, Mixvel_SeatAvailabilityRS.
The Name and ServiceCategory elements become optional in the scheme of the Mixvel_ServiceListRS and Mixvel_SeatAvailabilityRS response messages:
- .../Response/ALaCarteOffer/Name
- .../Response/ALaCarteOffer/ServiceCategory
Example of the structure of an additional service:
<ALaCarteOffer>
<ALaCarteOfferItem>
<Eligibility>
<EligibilityNotFlightAssociations>
<ProviderCode>DP</ProviderCode>
<ServiceDate>2024-08-21</ServiceDate>
<ServicePoint>LED</ServicePoint>
</EligibilityNotFlightAssociations>
<PaxRefID>Pax-1</PaxRefID>
</Eligibility>
<OfferItemID>0e739928-8fb5-4c3f-b466-48a831215365</OfferItemID>
<TicketDocTypeCode>Y</TicketDocTypeCode>
<Service>
<ServiceDefinitionRefID>d702db98-ecaa-49a4-a208-e33262e67ce9</ServiceDefinitionRefID>
<ServiceID>20a3ff1c-5df5-4478-bb36-c836a1f7e15c</ServiceID>
<ValidatingPartyRefID>072997f3-8776-4bca-b23a-6f65fc711c8f</ValidatingPartyRefID>
</Service>
<UnitPrice>
<BaseAmount CurCode="RUB">3500.00</BaseAmount>
<TotalAmount CurCode="RUB">3500.00</TotalAmount>
</UnitPrice>
</ALaCarteOfferItem>
</ALaCarteOffer>
Order/booking management¶
Adding OSI and SSR remarks to an order¶
Methods affected: Mixvel_OrderCreateRQ / Mixvel_OrderChangeRQ / Mixvel_OrderViewRS
The 1.4.0 release introduces changes to the schemes affecting backward compatibility of remarks transfer of new and old structures. OSI and SSR remarks need to be added using a new scheme (introduced in release 1.3.5) only.
The previous structure for adding remarks will no longer be supported.
The following structures are removed and are no longer supported:
- Mixvel_OrderChangeRQ/Request/DataLists/PaxList/Pax/Remark
- Mixvel_OrderViewRS/Response/DataLists/PaxList/Pax/Remark
In the new structure, remarks have been transferred from PaxList to DataList, a binding has been added to OfferID in OrderCreateRQ or to OrderID in OrderChangeRQ.
Creating order/booking Mixvel_OrderCreateRQ¶
Endpoint: /api/Order/Create
Adding SSR Remark
After the 1.4.0 release, the structure of adding SSR remark in the Mixvel_OrderCreateRQ request (when booking) is supported and is passed in the following form only:
<Request>
<DataLists>
…
<PaxSegmentRemarkList>
<PaxSegmentRemark>
<OfferRefID>…</OfferRefID> – link to the order (mandatory)
<PaxSegmentRefID>…</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<Type>other</Type> - type of remark
<Text>Test</Text> - text of the remark (optional)
</PaxSegmentRemark>
</PaxSegmentRemarkList>
…
</DataLists>
</Request>
The Text element becomes optional in the scheme of the Mixvel_OrderCreateRQ request:
- Mixvel_OrderCreateRQ/Request/DataLists/PaxSegmentRemarkList/PaxSegmentRemark/Text
The OfferRefID element becomes mandatory in the scheme of the Mixvel_OrderCreateRQ request:
- Mixvel_OrderCreateRQ/Request/DataLists/PaxSegmentRemarkList/PaxSegmentRemark/OfferRefID
Adding OSI Remark
After the 1.4.0 release, the structure of adding OSI remark in the Mixvel_OrderCreateRQ request (when booking) is supported and is passed in the following form only:
<Request>
<DataLists>
…
<OtherServiceInfoList>
<OtherServiceInfo>
<PaxRefID>Pax-1</PaxRefID>
<OfferRefID>…</OfferRefID> – link to the order (mandatory)
<Text>Test</Text> - text of the remark (optional)
</OtherServiceInfo>
</OtherServiceInfoList >
…
</DataLists>
</Request>
The Text element becomes optional in the scheme of the Mixvel_OrderCreateRQ request:
- Mixvel_OrderCreateRQ/Request/DataLists/OtherServiceInfoList/OtherServiceInfo/Text
The OfferRefID element becomes mandatory in the scheme of the Mixvel_OrderCreateRQ request:
- Mixvel_OrderCreateRQ/Request/DataLists/OtherServiceInfoList/OtherServiceInfo/OfferRefID
A unique identifier <RemarkID> is added to the Mixvel_OrderViewRS response message:
<Remark>
<PaxSegmentRefID>…</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<RemarkID>1d90d2f9-764e-4fd5-b84e-8576102bd6af</RemarkID>
<Type>other</Type>
<Text>Test</Text>
<StatusCode>HK</StatusCode>
</Remark>
The Text element becomes optional in the scheme of the Mixvel_OrderViewRS response message:
- Mixvel_OrderViewRS/Response/MixOrder/Order/OrderItem/Remark/Text
Order change Mixvel_OrderChangeRQ¶
Endpoint: /api/Order/Change
Adding SSR Remark
After the 1.4.0 release, the structure of adding SSR remark in the Mixvel_OrderChangeRQ request (oder change) is supported and is passed in the following form only:
<Request>
<DataLists>
…
<PaxSegmentRemarkList>
<PaxSegmentRemark>
<OrderRefID>…</OrderRefID> - link to the order (mandatory)
<PaxSegmentRefID>…</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<Type>other</Type> - type of remark
<Text>Test</Text> - text of the remark (optional)
<ActionType>add</ActionType> - action (add or delete) (mandatory)
</PaxSegmentRemark>
</PaxSegmentRemarkList>
</DataLists>
…
<MixOrder>
<MixOrderID>…</MixOrderID>
</MixOrder>
</Request>
The Text element becomes optional in the scheme of the Mixvel_OrderChangeRQ request:
- Mixvel_OrderChangeRQ/Request/DataLists/PaxSegmentRemarkList/PaxSegmentRemark/Text
The OrderRefID element becomes mandatory in the scheme of Mixvel_OrderChangeRQ request:
- Mixvel_OrderChangeRQ/Request/DataLists/PaxSegmentRemarkList/PaxSegmentRemark/OrderRefID
An optional RemarkID element is added to the request scheme:
Mixvel_OrderChangeRQ/Request/DataLists/PaxSegmentRemarkList/PaxSegmentRemark/RemarkID
Adding OSI Remark
After the 1.4.0 release, the structure of adding OSI remark in the Mixvel_OrderChangeRQ request (oder change) is supported and is passed in the following form only:
<Request>
<DataLists>
…
<OtherServiceInfoList>
<OtherServiceInfo>
<OrderRefID>…</OrderRefID> - link to the order (mandatory)
<PaxRefID>Pax-1</PaxRefID>
<Text>Test</Text> - text of the remark (optional)
<ActionType>add</ActionType> - action (add or delete) (mandatory)
</OtherServiceInfo>
</OtherServiceInfoList>
…
</DataLists>
<MixOrder>
<MixOrderID>…</MixOrderID>
</MixOrder>
</Request>
The Text element becomes optional in the scheme of the Mixvel_OrderChangeRQ request:
- Mixvel_OrderChangeRQ /Request/DataLists/OtherServiceInfoList/OtherServiceInfo/Text
The OrderRefID element becomes mandatory in the scheme of Mixvel_OrderChangeRQ request:
- Mixvel_OrderChangeRQ/Request/DataLists/OtherServiceInfoList/OtherServiceInfo/OrderRefID
An unique identifier <RemarkID> is added to the Mixvel_OrderViewRS response message:
<Remark>
<PaxSegmentRefID>…</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<RemarkID>1d90d2f9-764e-4fd5-b84e-8576102bd6af</RemarkID>
<Type>other</Type>
<Text>Test</Text>
<StatusCode>HK</StatusCode>
</Remark>
The Text element becomes optional in the scheme of the Mixvel_OrderViewRS response message:
- Mixvel_OrderViewRS/Response/MixOrder/Order/OrderItem/Remark/Text
Adding loyalty card to an order¶
Methods affected: Mixvel_OrderCreateRQ / Mixvel_OrderChangeRQ / Mixvel_OrderViewRS
Creating order/booking Mixvel_OrderCreateRQ¶
Endpoint: /api/Order/Create
The LoyaltyProgramAccount array is going to be deleted from PaxList in the 1.4.0 release:
Mixvel_OrderCreateRQ/Request/DataLists/PaxList/Pax/LoyaltyProgramAccount
The array is transferred to:
Mixvel_OrderCreateRQ/Request/DataLists/LoyaltyProgramAccountList
Example of adding a loyalty card information in OrderCreateRQ request:
<DataLists>
…
<LoyaltyProgramAccountList>
<LoyaltyProgramAccount>
<AccountNumber>123456789</AccountNumber>
<LoyaltyProgram>
<Carrier>
<AirlineDesigCode>SU</AirlineDesigCode>
</Carrier>
</LoyaltyProgram>
<OfferRefID>token</OfferRefID>
<PaxRefID>Pax-1</PaxRefID>
</LoyaltyProgramAccount>
</LoyaltyProgramAccountList>
...
</DataLists>
In the response message Mixvel_OrderViewRS the information will be displayed as:
<LoyaltyProgramAccountList>
<LoyaltyProgramAccount>
<AccountNumber>123456789</AccountNumber>
<LoyaltyProgram>
<Carrier>
<AirlineDesigCode>DP</AirlineDesigCode>
</Carrier>
</LoyaltyProgram>
<LoyaltyProgramID>token</LoyaltyProgramID>
<PaxSegmentRefID>token</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<OrderRefID>96829-230911-OAH5765</OrderRefID>
<StatusCode>HK</StatusCode>
</LoyaltyProgramAccount>
</LoyaltyProgramAccountList>
Order/Booking Management Mixvel_OrderChangeRQ¶
Endpoint: /api/Order/Change
The LoyaltyProgramAccount array is going to be deleted from PaxList in the 1.4.0 release:
- Mixvel_OrderChangeRQ/Request/DataLists/PaxList/Pax/LoyaltyProgramAccount
The array is transferred to:
- Mixvel_OrderChangeRQ/Request/DataLists/LoyaltyProgramAccountList
Example of adding a loyalty card information in OrderChangeRQ request:
<DataLists>
…
<LoyaltyProgramAccountList>
<LoyaltyProgramAccount>
<AccountNumber>123456789</AccountNumber>
<LoyaltyProgram>
<Carrier>
<AirlineDesigCode>DP</AirlineDesigCode>
</Carrier>
</LoyaltyProgram>
<PaxSegmentRefID>token</PaxSegmentRefID>
<OrderRefID>token</OfferRefID>
<PaxRefID>Pax-1</PaxRefID>
<ActionType>add</ActionType>
</LoyaltyProgramAccount>
<LoyaltyProgramAccountList>
…
</DataLists>
In the response message Mixvel_OrderViewRS the information will be displayed as:
<LoyaltyProgramAccountList>
<LoyaltyProgramAccount>
<AccountNumber>123456789</AccountNumber>
<LoyaltyProgram>
<Carrier>
<AirlineDesigCode>DP</AirlineDesigCode>
</Carrier>
</LoyaltyProgram>
<LoyaltyProgramID>token</LoyaltyProgramID>
<PaxSegmentRefID>token</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<OrderRefID>96829-230911-OAH5765</OrderRefID>
<StatusCode>HK</StatusCode>
</LoyaltyProgramAccount>
</LoyaltyProgramAccountList>
View order/booking status Mixvel_OrderRetrieveRQ¶
Endpoint: /api/Order/Retrieve
The ability to view booking status by PNR number in the Mixvel_OrderRetrieveRQ request will be done using a new BookingRefFilterCriteria element.
Example of a correct Mixvel_OrderRetrieveRQ request to view booking status by PNR number:
<Request>
<OrderFilterCriteria>
<BookingRefFilterCriteria>
<BookingRefID>244T6P</BookingRefID>
</BookingRefFilterCriteria>
</OrderFilterCriteria>
</Request>
Viewing booking information from another GDS in a Mixvel_OrderRetrieveRQ request is also done using the ExternalOrder element. This makes the following elements in the ExternalOrder mandatory:
- Mixvel_OrderRetrieveRQ/Request/OrderFilterCriteria/ExternalOrder/Surname
- Mixvel_OrderRetrieveRQ/Request/OrderFilterCriteria/ExternalOrder/AirlineDesigCode
It also changes the order of the elements at the:
Mixvel_OrderRetrieveRQ/Request/OrderFilterCriteria/ExternalOrder
Example of a correct request to view booking information from another GDS:
<Request>
<OrderFilterCriteria>
<ExternalOrder>
<AirlineDesigCode>A9</AirlineDesigCode>
<BookingRefID>1CG564</BookingRefID>
<CarrierFlightNumber>123</CarrierFlightNumber>
<Surname>CLOCK</Surname>
</ExternalOrder>
</OrderFilterCriteria>
</Request>
Order/booking import¶
Endpoint: /api/Order/Import
- The DataLists structure is going to be removed from the Mixvel_OrderImportRQ request. The Surname element is transferred to ExternalOrderRequest and ExternalTicketRequest structures.
- The ExternalTicketOrderRequest element is going to be renamed to ExternalTicketRequest.
- An .../ExternalTicketRequest/AirlineDesigCode element is going to be removed.
- Elements in ExternalOrderRequest will be arranged alphabetically.
Examples of correct requests Mixvel_OrderImportRQ:
ExternalOrderRequest
- import by PNR number
<Request>
<ExternalOrderRequest>
<BookingRefID>0W0S86</BookingRefID>
<SystemCode>Tch</SystemCode>
<Surname>GLAGOLEV</Surname>
</ExternalOrderRequest>
</Request>
- importing with the ForceImport flag after changing an order in third-party systems
<Request>
<ExternalOrderRequest>
<BookingRefID>225F42</BookingRefID>
<ForceImport>true</ForceImport>
<Surname>PETROV</Surname>
<SystemCode>Tch</SystemCode>
</ExternalOrderRequest>
</Request>
- capturing a booking from another GDS (functionality available only for airlines)
<Request>
<ExternalOrderRequest>
<AirlineDesigCode>N4</AirlineDesigCode>
<BookingRefID>183G49</BookingRefID>
<CarrierFlightNumber>456</CarrierFlightNumber>
<Surname>PETROV</Surname>
<SystemCode>Leonardo</SystemCode>
</ExternalOrderRequest>
</Request>
ExternalTicketRequest
- import by ticket number
<Request>
<ExternalTicketRequest>
<TicketNumber>2986170029619</TicketNumber>
</ExternalTicketRequest>
</Request>
Structure of the message OrderViewRS¶
Amount element¶
The Amount element becomes optional in the scheme of the Mixvel_OrderViewRS response message:
- Mixvel_OrderViewRS/Response/PaymentFunctions/PaymentProcessingSummary/Amount
Example of the structure:
<PaymentFunctions>
<OrderAssociation>
<OrderRefID>01138-240730-OOE5293</OrderRefID>
</OrderAssociation>
<PaymentProcessingSummary>
<PaymentID>0fc10cfc-f391-4944-8b7b-7c12daa66fd6</PaymentID>
<PaymentProcessingDetailsPaymentMethod>
<OtherPaymentMethod/>
</PaymentProcessingDetailsPaymentMethod>
</PaymentProcessingSummary>
</PaymentFunctions>
OrderRef and OrderAssociation elements¶
- The <OrderRef> becomes mandatory in the structure:
Mixvel_OrderViewRS/Response/TicketDocInfo/OrderRef
- The <OrderAssociation> becomes mandatory in the structure:
Mixvel_OrderViewRS/Response/PaymentFunctions/PaymentFunctionsType/OrderAssociation
Changing the number of AccountCode elements¶
The maximum number of AccountCode elements changes in the structure:
Mixvel_OrderViewRQ/Response/MixOrder/Order/OrderItem/FareDetail/AccountCode
Previously, the number of elements in the structure was not limited. After release 1.4.0, 0 to 1 occurrence of an element is possible.
Changing the number of OrderItemID elements¶
The maximum number of OrderItemID elements changes in the structure:
Mixvel_OrderViewRQ/Response/TicketDocInfo/OrderRef/OrderItemID
Previously, the number of elements in the structure was not limited. After release 1.4.0, 0 to 1 occurrence of an element is possible due to a change in the display logic of OrderItem multi-coupon EMD.
Deleting SeatProfileRefID from ServiceDefinition¶
The SeatProfileRefID will be removed from the structure:
Mixvel_OrderViewRS/Response/DataLists/ServiceDefinitionList/ServiceDefinition/ServiceDefinitionAssociation/SeatProfileRef/SeatProfileRefID
The SeatProfileRefID link will still be displayed in the structure:
Mixvel_OrderViewRS/Response/MixOrder/Order/OrderItem/Service/ServiceAssociations/SelectedSeat/Seat/SeatProfileRefID
Example of the Service structure in which the element is saved:
<Service>
<PaxRefID>Pax-1</PaxRefID>
<ValidatingPartyRefID>c7eb4492-08e8-467f-a2e2-5c533fa97a53</ValidatingPartyRefID>
<ServiceAssociations>
<SelectedSeat>
<Seat>
<ColumnID>D</ColumnID>
<RowNumber>16</RowNumber>
<SeatProfileRefID>f346a608-4da1-4cca-a03b-d8a90ea69b49</SeatProfileRefID>
</Seat>
<SeatAssignmentAssociations>
<PaxSegmentRef>
<PaxSegmentRefID>ff4cb99f-7ef0-4c9d-b42a-92e476efeaed</PaxSegmentRefID>
</PaxSegmentRef>
</SeatAssignmentAssociations>
<ServiceDefinitionRefID>fea347a7-5e17-4817-bd78-b12208f8c02c</ServiceDefinitionRefID>
</SelectedSeat>
</ServiceAssociations>
<ServiceID>467a05ad-5a57-46f1-8971-d68b860a452e</ServiceID>
<OriginServiceRef>14</OriginServiceRef>
<StatusCode>HD</StatusCode>
</Service>
Exchange of paid order OrderReshopRQ¶
Endpoint:/api/Order/Reshop
The logic for calculating of the total amount for automatic exchange calculation per exchange will be changed.
The following elements are going to be removed from the AddPrice structure:
- Mixvel_OrderReshopRS/Response/ReshopOffers/Offer/AddOfferItem/ReshopPrice/AddPrice/FareDetail
- Mixvel_OrderReshopRS/Response/ReshopOffers/Offer/AddOfferItem/ReshopPrice/AddPrice/ServiceAssociations
- Mixvel_OrderReshopRS/Response/ReshopOffers/Offer/AddOfferItem/ReshopPrice/AddPrice/Price
In release 1.3.8, structures for detailing the cost of exchange will be added:
DiffPrice - structure for calculating the cost of an additional payment for an exchange, taking into account the difference in tariff, difference in taxes and fees. This structure will calculate the difference between the paid amount and the new amount, including the exchange fee. The TotalAmount value in the DiffPrice structure will show the amount to be exchanged, including fees.
- .../AddOfferItem/ReshopPrice/AddPrice/DiffPrice
NewPrice - structure for calculating the cost of coupons for new tickets.
- .../AddOfferItem/ReshopPrice/AddPrice/NewPrice
The display of interchange fees will only be returned in the structure:
- Mixvel_OrderReshopRS/Response/ReshopResults/ReshopOffers/Offer/AddOfferItem/ReshopPrice/AddPrice/DiffPrice/FareDetail/Price/Fee
Example of displaying the exchange fee:
<Price>
<BaseAmount CurCode="RUB">37930.00</BaseAmount>
<BaseAmountGuaranteeTimeLimitDateTime>2024-09-28T16:54:00</BaseAmountGuaranteeTimeLimitDateTime>
<Fee>
<Amount CurCode="RUB">2800.00</Amount>
<FeeCode>CP</FeeCode>
</Fee>
</Price>
Also in release 1.4.0 the PenaltyList display logic will be changed. The PenaltyList structure will indicate the amount of fees for a specific offer (the sum of all Fees) from all structures:
- .../AddOfferItem/ReshopRrice/AddPrice/DiffPrice/FareDetail/Price/Fee/Amount.
The final coupon value of the a ticket will not include exchange Fees:
- .../NewPrice/FareDetail/FareComponent/Price/TotalAmount
The value (TotalAmount) of the new ticket coupon will include the sum of the fare and taxes:
-
BaseAmount (EquivAmount) - fare amount;
-
FareComponent/Price/TaxSummary/TotalAmount - tax amount.
Until Deprecated Features 1.4.0 is released, the ...Addprice/Faredetail and ...Addprice/Price structures will be supported.
Example of exchange calculation structure in Mixvel_OrderReshopRS in version 1.4.0:
Show the example of Mixvel_OrderReshopRS on this page
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body>
<MessageInfo MessageId="7f326a0b-9af3-4e3d-90fd-e4134a79c335" ReplyTo="703423d1-595c-49f5-98c2-5dcabe950276" TimeSent="2024-11-20T08:09:21.1799726Z"/>
<AppData>
<Reshop:Mixvel_OrderReshopRS xmlns:Reshop="https://www.mixvel.com/API/XSD/Mixvel_OrderReshopRS/1_00">
<Response>
<ReshopResults>
<ReshopOffers>
<Offer OrderId="96829-241120-OEE4922">
<AddOfferItem>
<OfferItemID>c89dabad-73b5-4866-b63c-c4feb2ce7918</OfferItemID>
<ReshopPrice>
<AddPrice>
<DiffPrice>
<FareDetail>
<ClosedFare>false</ClosedFare>
<FareComponent>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
</CabinType>
<TicketCoupon>1</TicketCoupon>
<FareBasisCode>ULGT1</FareBasisCode>
<FareRule>
<RuleCode>EL01</RuleCode>
</FareRule>
<PaxSegmentRefID>e555346e-e3ff-43ba-9407-972f81931615</PaxSegmentRefID>
<Price>
<BaseAmountGuaranteeTimeLimitDateTime>2025-02-01T09:15:00</BaseAmountGuaranteeTimeLimitDateTime>
<EquivAmount CurCode="NUC">0.00</EquivAmount>
<Fee>
<Amount CurCode="RUB">5275.00</Amount>
<FeeCode>CP</FeeCode>
</Fee>
<TaxSummary>
<Tax>
<Amount CurCode="RUB">317.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">739.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">-317.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">-739.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<TotalTaxAmount CurCode="RUB">0.00</TotalTaxAmount>
</TaxSummary>
<TotalAmount CurCode="RUB">5275.00</TotalAmount>
</Price>
<PriceClassRefID>e20700fe-fff8-416a-beb4-0887b7a5f94f</PriceClassRefID>
<RBD>
<RBD_Code>U</RBD_Code>
<Availability>9</Availability>
</RBD>
</FareComponent>
<PaxRefID>Pax-1</PaxRefID>
<Price>
<BaseAmountGuaranteeTimeLimitDateTime>2025-02-01T09:15:00</BaseAmountGuaranteeTimeLimitDateTime>
<EquivAmount CurCode="NUC">0.00</EquivAmount>
<Fee>
<Amount CurCode="RUB">5275.00</Amount>
<FeeCode>CP</FeeCode>
</Fee>
<TaxSummary>
<Tax>
<Amount CurCode="RUB">0.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">0.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<TotalTaxAmount CurCode="RUB">0.00</TotalTaxAmount>
</TaxSummary>
<TotalAmount CurCode="RUB">5275.00</TotalAmount>
</Price>
</FareDetail>
<Price>
<BaseAmountGuaranteeTimeLimitDateTime>2025-02-01T09:15:00</BaseAmountGuaranteeTimeLimitDateTime>
<EquivAmount CurCode="NUC">0.00</EquivAmount>
<Fee>
<Amount CurCode="RUB">5275.00</Amount>
<FeeCode>CP</FeeCode>
</Fee>
<TaxSummary>
<Tax>
<Amount CurCode="RUB">0.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">0.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<TotalTaxAmount CurCode="RUB">0.00</TotalTaxAmount>
</TaxSummary>
<TotalAmount CurCode="RUB">5275.00</TotalAmount>
</Price>
</DiffPrice>
<NewPrice>
<FareDetail>
<ClosedFare>false</ClosedFare>
<FareComponent>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
</CabinType>
<TicketCoupon>1</TicketCoupon>
<FareBasisCode>ULGT1</FareBasisCode>
<FareRule>
<RuleCode>EL01</RuleCode>
</FareRule>
<PaxSegmentRefID>e555346e-e3ff-43ba-9407-972f81931615</PaxSegmentRefID>
<Price>
<BaseAmount CurCode="RUB">4010.00</BaseAmount>
<BaseAmountGuaranteeTimeLimitDateTime>2025-02-01T09:15:00</BaseAmountGuaranteeTimeLimitDateTime>
<EquivAmount CurCode="NUC">4010.00</EquivAmount>
<Fee>
<Amount CurCode="RUB">5275.00</Amount>
<FeeCode>CP</FeeCode>
</Fee>
<TaxSummary>
<Tax>
<Amount CurCode="RUB">317.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">739.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<TotalTaxAmount CurCode="RUB">1056.00</TotalTaxAmount>
</TaxSummary>
<TotalAmount CurCode="RUB">5066.00</TotalAmount>
</Price>
<PriceClassRefID>e20700fe-fff8-416a-beb4-0887b7a5f94f</PriceClassRefID>
<RBD>
<RBD_Code>U</RBD_Code>
<Availability>9</Availability>
</RBD>
</FareComponent>
<PaxRefID>Pax-1</PaxRefID>
<Price>
<BaseAmount CurCode="RUB">4010.00</BaseAmount>
<BaseAmountGuaranteeTimeLimitDateTime>2025-02-01T09:15:00</BaseAmountGuaranteeTimeLimitDateTime>
<EquivAmount CurCode="NUC">4010.00</EquivAmount>
<Fee>
<Amount CurCode="RUB">5275.00</Amount>
<FeeCode>CP</FeeCode>
</Fee>
<TaxSummary>
<Tax>
<Amount CurCode="RUB">317.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">739.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<TotalTaxAmount CurCode="RUB">1056.00</TotalTaxAmount>
</TaxSummary>
<TotalAmount CurCode="RUB">5066.00</TotalAmount>
</Price>
</FareDetail>
<Price>
<BaseAmount CurCode="RUB">4010.00</BaseAmount>
<BaseAmountGuaranteeTimeLimitDateTime>2025-02-01T09:15:00</BaseAmountGuaranteeTimeLimitDateTime>
<EquivAmount CurCode="NUC">4010.00</EquivAmount>
<TaxSummary>
<Tax>
<Amount CurCode="RUB">317.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">739.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<TotalTaxAmount CurCode="RUB">1056.00</TotalTaxAmount>
</TaxSummary>
<TotalAmount CurCode="RUB">5066.00</TotalAmount>
</Price>
</NewPrice>
</AddPrice>
</ReshopPrice>
<Service>
<PaxRefID>Pax-1</PaxRefID>
<ValidatingPartyRefID>06e33e11-91ea-4fcb-85c8-874ab1f5307d</ValidatingPartyRefID>
<ServiceAssociations>
<PaxSegmentRef>
<PaxSegmentRefID>e555346e-e3ff-43ba-9407-972f81931615</PaxSegmentRefID>
</PaxSegmentRef>
</ServiceAssociations>
<ServiceID>8a15ed5c-f209-4556-920d-3409e92a7657</ServiceID>
</Service>
</AddOfferItem>
<BaggageAssociations>
<BaggageAllowanceRefID>413a705e-bf64-4933-810d-19335fbc8e57</BaggageAllowanceRefID>
<BaggageFlightAssociations>
<PaxSegmentRef>
<PaxSegmentRefID>e555346e-e3ff-43ba-9407-972f81931615</PaxSegmentRefID>
</PaxSegmentRef>
</BaggageFlightAssociations>
<PaxRefID>Pax-1</PaxRefID>
</BaggageAssociations>
<BaggageAssociations>
<BaggageAllowanceRefID>44cae626-6d29-4785-af34-4d6704ba689e</BaggageAllowanceRefID>
<BaggageFlightAssociations>
<PaxSegmentRef>
<PaxSegmentRefID>e555346e-e3ff-43ba-9407-972f81931615</PaxSegmentRefID>
</PaxSegmentRef>
</BaggageFlightAssociations>
<PaxRefID>Pax-1</PaxRefID>
</BaggageAssociations>
<OfferExpirationTimeLimitDateTime>2024-11-20T08:54:21.100753Z</OfferExpirationTimeLimitDateTime>
<OfferID>bcff890e-6565-4e54-918e-47223b55a72c</OfferID>
<OwnerCode>TCH</OwnerCode>
<PenaltyRefID>94a3d773-60d1-4436-b6cc-d73bb3f38c31</PenaltyRefID>
<TotalPrice>
<BaseAmount CurCode="RUB">4010.00</BaseAmount>
<BaseAmountGuaranteeTimeLimitDateTime>2025-02-01T09:15:00</BaseAmountGuaranteeTimeLimitDateTime>
<EquivAmount CurCode="NUC">4010.00</EquivAmount>
<TaxSummary>
<Tax>
<Amount CurCode="RUB">317.00</Amount>
<TaxCode>YQ</TaxCode>
</Tax>
<Tax>
<Amount CurCode="RUB">739.00</Amount>
<TaxCode>YR</TaxCode>
</Tax>
<TotalTaxAmount CurCode="RUB">1056.00</TotalTaxAmount>
</TaxSummary>
<TotalAmount CurCode="RUB">10341.00</TotalAmount>
</TotalPrice>
</Offer>
</ReshopOffers>
</ReshopResults>
<DataLists>
<BaggageAllowanceList>
<BaggageAllowance>
<BaggageAllowanceID>413a705e-bf64-4933-810d-19335fbc8e57</BaggageAllowanceID>
<DescText>No</DescText>
<TypeCode>Checked</TypeCode>
</BaggageAllowance>
<BaggageAllowance>
<BaggageAllowanceID>44cae626-6d29-4785-af34-4d6704ba689e</BaggageAllowanceID>
<DescText>PC</DescText>
<PieceAllowance>
<TotalQty>1</TotalQty>
</PieceAllowance>
<TypeCode>CarryOn</TypeCode>
<Allowed>
<Name>CARRY10KG 22LB 55L X 40W X 25H (08A)</Name>
<LimitValue>1</LimitValue>
<DimensionAllowance>
<BaggageDimensionCategory>Length</BaggageDimensionCategory>
<MaxMeasure UnitCode="Centimetre">55</MaxMeasure>
</DimensionAllowance>
<DimensionAllowance>
<BaggageDimensionCategory>Width</BaggageDimensionCategory>
<MaxMeasure UnitCode="Centimetre">40</MaxMeasure>
</DimensionAllowance>
<DimensionAllowance>
<BaggageDimensionCategory>Height</BaggageDimensionCategory>
<MaxMeasure UnitCode="Centimetre">25</MaxMeasure>
</DimensionAllowance>
<WeightAllowance>
<MaximumWeightMeasure UnitCode="Kilogram">10</MaximumWeightMeasure>
</WeightAllowance>
<WeightAllowance>
<MaximumWeightMeasure UnitCode="Pound">22</MaximumWeightMeasure>
</WeightAllowance>
</Allowed>
</BaggageAllowance>
</BaggageAllowanceList>
<PaxList>
<Pax>
<AgeMeasure>27</AgeMeasure>
<ContactInfoRefID>Contact-1</ContactInfoRefID>
<IdentityDoc>
<ExpiryDate>2025-01-01</ExpiryDate>
<IdentityDocID>4510000562</IdentityDocID>
<IdentityDocTypeCode>PS</IdentityDocTypeCode>
<IssuingCountryCode>RU</IssuingCountryCode>
<Surname>IVANOV</Surname>
</IdentityDoc>
<Individual>
<Birthdate>1997-07-07</Birthdate>
<GenderCode>M</GenderCode>
<GivenName>IVAN</GivenName>
<MiddleName>IVANOVICH</MiddleName>
<Surname>IVANOV</Surname>
<PrefixName>MR</PrefixName>
</Individual>
<OrderRefID>96829-241120-OEE4922</OrderRefID>
<PaxID>Pax-1</PaxID>
<PTC>ADT</PTC>
</Pax>
</PaxList>
<PaxSegmentList>
<PaxSegment>
<Arrival>
<ScheduledDateTime>2025-02-01T10:40:00</ScheduledDateTime>
<AircraftScheduledDateTime>2025-02-01T10:40:00</AircraftScheduledDateTime>
<IATA_LocationCode>MSQ</IATA_LocationCode>
<StationName>Минск(Минск Интл.)</StationName>
</Arrival>
<DatedOperatingLeg>
<Arrival>
<ScheduledDateTime>2025-02-01T10:40:00</ScheduledDateTime>
<AircraftScheduledDateTime>2025-02-01T10:40:00</AircraftScheduledDateTime>
<IATA_LocationCode>MSQ</IATA_LocationCode>
<StationName>Минск(Минск Интл.)</StationName>
</Arrival>
<CarrierType>
<CarrierTypeCode>E75</CarrierTypeCode>
</CarrierType>
<CarrierAircraftType>
<CarrierAircraftTypeCode>E75</CarrierAircraftTypeCode>
</CarrierAircraftType>
<DatedOperatingLegID>7c3333f0-2646-443c-a835-cda86544a6dd</DatedOperatingLegID>
<Dep>
<ScheduledDateTime>2025-02-01T09:15:00</ScheduledDateTime>
<AircraftScheduledDateTime>2025-02-01T09:15:00</AircraftScheduledDateTime>
<IATA_LocationCode>VKO</IATA_LocationCode>
<StationName>Москва(Внуково)</StationName>
</Dep>
</DatedOperatingLeg>
<Dep>
<ScheduledDateTime>2025-02-01T09:15:00</ScheduledDateTime>
<AircraftScheduledDateTime>2025-02-01T09:15:00</AircraftScheduledDateTime>
<IATA_LocationCode>VKO</IATA_LocationCode>
<StationName>Москва(Внуково)</StationName>
</Dep>
<Duration>PT1H25M</Duration>
<Distance UnitCode="Mileage">414</Distance>
<MarketingCarrierInfo>
<CarrierDesigCode>B2</CarrierDesigCode>
<MarketingCarrierFlightNumberText>982</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
<SegmentType>Aircraft</SegmentType>
<PaxSegmentID>e555346e-e3ff-43ba-9407-972f81931615</PaxSegmentID>
</PaxSegment>
</PaxSegmentList>
<PenaltyList>
<Penalty>
<PaxRefID>Pax-1</PaxRefID>
<PenaltyID>94a3d773-60d1-4436-b6cc-d73bb3f38c31</PenaltyID>
<Price>
<BaseAmount CurCode="RUB">5275.00</BaseAmount>
<TotalAmount CurCode="RUB">5275.00</TotalAmount>
</Price>
<TypeCode>Change</TypeCode>
</Penalty>
</PenaltyList>
<PriceClassList>
<PriceClass>
<Code>EL</Code>
<Desc>
<Access>C</Access>
<DescText>ВЫБОР МЕСТА (0B5)</DescText>
</Desc>
<Desc>
<Access>F</Access>
<DescText>РУЧ КЛАДЬ 10КГ 22Ф ДО 45Д115СМ (0MJ)</DescText>
</Desc>
<Desc>
<Access>N</Access>
<DescText>EXCESS PIECE 23KG SMT (0C3)</DescText>
</Desc>
<Desc>
<Access>N</Access>
<DescText>EXCESS PIECE 32KG FLX BIZ (0C6)</DescText>
</Desc>
<Desc>
<Access>N</Access>
<DescText>SABRE TKT UPTO 23KG (0GO)</DescText>
</Desc>
<Name>ECONOMY LIGHT</Name>
<PriceClassID>e20700fe-fff8-416a-beb4-0887b7a5f94f</PriceClassID>
</PriceClass>
</PriceClassList>
<ValidatingPartyList>
<ValidatingParty>
<ValidatingPartyID>06e33e11-91ea-4fcb-85c8-874ab1f5307d</ValidatingPartyID>
<ValidatingPartyCode>B2</ValidatingPartyCode>
<ValidatingPartyName>Белавиа</ValidatingPartyName>
<ValidatingPartyDesigCode>628</ValidatingPartyDesigCode>
</ValidatingParty>
</ValidatingPartyList>
</DataLists>
</Response>
</Reshop:Mixvel_OrderReshopRS>
</AppData>
</Body>
</MixEnv:Envelope>