Deprecated Features in release 1.5.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 end of January 2026 we plan the release 1.5.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.5.0.
In case of any questions please feel free to contact us via the mailbox support@mixvel.com.
General changes¶
Displaying city/port code in LocationCode¶
In 1.5.0 release, the <IATA_LocationCode> parameter is removed. This change affects the AirShoppingRQ, OrderReshopRQ, AvailabilityRQ, and AirlineProfileRQ request structures, as well as the AirShoppingRS, OfferPriceRS, OrderViewRS, OrderReshopRS, AvailabilityRS, AirlineProfileRS, SeatAvailabilityRS and ServiceListRS response messages. The Standard attribute for specifying the owner of the city/port code is also removed.
The parameter is removed in the query schema:
-
.../OriginDestCriteria/DestArrivalCriteria/IATA_LocationCode
-
.../OriginDestCriteria/OriginDepCriteria/IATA_LocationCode
The parameter is removed in the response message schema:
-
.../Response/DataLists/PaxSegmentList/PaxSegment/Arrival/IATA_LocationCode
-
.../Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/Arrival/IATA_LocationCode
-
.../Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/Dep/IATA_LocationCode
-
.../Response/DataLists/PaxSegmentList/PaxSegment/Dep/IATA_LocationCode
Instead, the <LocationCode> parameter will be used with the Standard attribute of the city/port code owner (IATA or TCH).
The updated structures are available in the MixVel API starting with release 1.4.6.
Example of structures after 1.5.0 release¶
Example of Mixvel_AirShoppingRQ:
Show request example
<?xml version="1.0"?>
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body>
<MessageInfo MessageId="0a5a977c-bfc6-4464-96b6-8dda03141592" TimeSent="2025-10-24T19:53:14Z"/>
<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>
<LocationCode Standard="IATA">MOW</LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2025-12-25</Date>
<LocationCode Standard="TCH">СПТ</LocationCode>
</OriginDepCriteria>
</OriginDestCriteria>
</FlightRequestOriginDestinationsCriteria>
</FlightRequest>
<Paxs>
<Pax>
<PaxID>Pax-1</PaxID>
<PTC>ADT</PTC>
</Pax>
</Paxs>
</Request>
</shop:Mixvel_AirShoppingRQ>
</AppData>
</Body>
</MixEnv:Envelope>
Example of Mixvel_OrderReshopRQ:
Show request example
<?xml version="1.0"?>
<MixEnv:Envelop xmlns:MixEnv="http://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body id="ID1">
<MessageInfo MessageId="703423d1-595c-49f5-98c2-5dcabe950276" TimeSent="2025-10-12T12:17:51Z"/>
<AppData>
<m:Mixvel_OrderReshopRQ xmlns:m="https://www.mixvel.com/API/XSD/Mixvel_OrderReshopRQ/1_00">
<Request xmlns="">
<MixOrder>
<MixOrderID>01138-251028-MTY2774</MixOrderID>
</MixOrder>
<UpdateOrder>
<ReshopOrder>
<ReshopOrderChoice>
<ServiceOrder>
<AddOfferItems>
<OriginDestCriteria>
<CabinType>
<CabinTypeCode>Economy</CabinTypeCode>
</CabinType>
<DestArrivalCriteria>
<LocationCode Standard="TCH">СПТ</LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2025-11-13</Date>
<LocationCode Standard="IATA">MOW</LocationCode>
</OriginDepCriteria>
</OriginDestCriteria>
<PaxSegmentRefID>0f1d410f-a1b0-4157-8d6b-dcb10e8fcab5</PaxSegmentRefID>
</AddOfferItems>
<OrderRefID>01138-251028-OTY2775</OrderRefID>
</ServiceOrder>
</ReshopOrderChoice>
</ReshopOrder>
</UpdateOrder>
<PaymentFunctions>
<PaymentProcessingDetails>
<PaymentProcessingDetailsPaymentMethod>
<OtherPaymentMethod/>
</PaymentProcessingDetailsPaymentMethod>
</PaymentProcessingDetails>
</PaymentFunctions>
</Request>
</m:Mixvel_OrderReshopRQ>
</AppData>
</Body>
</MixEnv:Envelop>
Example of Mixvel_AvailabilityRQ:
Show request example
<?xml version="1.0"?>
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body id="ID1">
<MessageInfo MessageId="e5cc6d38-73ad-42e0-8783-06342504cdd7" TimeSent="2025-10-23T14:11:00Z"/>
<AppData>
<Shop:Mixvel_AvailabilityRQ xmlns:Shop="https://www.mixvel.com/API/XSD/Mixvel_AvailabilityRQ/1_00">
<Request>
<FlightRequest>
<OriginDestCriteria>
<CarrierPrefRefID>Carrier-0</CarrierPrefRefID>
<DestArrivalCriteria>
<LocationCode Standard="IATA">MOW</LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<Date>2025-11-08</Date>
<LocationCode Standard="IATA">LED</LocationCode>
</OriginDepCriteria>
</OriginDestCriteria>
</FlightRequest>
<ShoppingCriteria>
<CarrierCriteria>
<Carrier>
<AirlineDesigCode>SU</AirlineDesigCode>
</Carrier>
<CarrierPrefID>Carrier-0</CarrierPrefID>
</CarrierCriteria>
<FlightCriteria>
<RBD>
<RBD_Code>R</RBD_Code>
</RBD>
</FlightCriteria>
<SegmentStatusCriteria>
<Open>true</Open>
<Request>true</Request>
<Waitlist>true</Waitlist>
</SegmentStatusCriteria>
</ShoppingCriteria>
</Request>
</Shop:Mixvel_AvailabilityRQ>
</AppData>
</Body>
</MixEnv:Envelope>
Example of Mixvel_AirlineProfileRQ:
Show request example
<?xml version="1.0"?>
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body>
<MessageInfo MessageId="0295a18c-6cf4-4415-8a18-4dfb863abefb" TimeSent="2025-10-22T06:01:00Z"/>
<AppData>
<m:Mixvel_AirlineProfileRQ xmlns:m="https://www.mixvel.com/API/XSD/Mixvel_AirlineProfileRQ/1_01">
<Request xmlns="">
<AirScheduleFilterCriteria>
<ScheduleRequest>
<OriginDestCriteria>
<DestArrivalCriteria>
<LocationCode Standard="IATA">LED</LocationCode>
</DestArrivalCriteria>
<OriginDepCriteria>
<DateRangeStart>2025-11-25</DateRangeStart>
<DateRangeEnd>2025-11-27</DateRangeEnd>
<LocationCode Standard="IATA">MOW</LocationCode>
</OriginDepCriteria>
</OriginDestCriteria>
</ScheduleRequest>
</AirScheduleFilterCriteria>
</Request>
</m:Mixvel_AirlineProfileRQ>
</AppData>
</Body>
</MixEnv:Envelope>
Example of PaxSegment structure with new parameters in response messages:
<PaxSegment>
<Arrival>
<ScheduledDateTime>2025-12-25T19:45:00</ScheduledDateTime>
<DateShift>0</DateShift>
<LocationCode Standard="IATA">VKO</LocationCode>
<StationName>Москва(Внуково)</StationName>
<TerminalName>A</TerminalName>
</Arrival>
<DatedOperatingLeg>
<Arrival>
<ScheduledDateTime>2025-12-25T19:45:00</ScheduledDateTime>
<LocationCode Standard="IATA">VKO</LocationCode>
<StationName>Москва(Внуково)</StationName>
<TerminalName>A</TerminalName>
</Arrival>
<CarrierType>
<CarrierTypeCode>SU9</CarrierTypeCode>
</CarrierType>
<DatedOperatingLegID>e5a29d8d-3629-4c98-98db-1d2c21dc60b5</DatedOperatingLegID>
<Dep>
<ScheduledDateTime>2025-12-25T18:00:00</ScheduledDateTime>
<LocationCode Standard="IATA">LED</LocationCode>
<StationName>Санкт-Петербург(Пулково)</StationName>
<TerminalName>1</TerminalName>
</Dep>
</DatedOperatingLeg>
<Dep>
<ScheduledDateTime>2025-12-25T18:00:00</ScheduledDateTime>
<DateShift>0</DateShift>
<LocationCode Standard="IATA">LED</LocationCode>
<StationName>Санкт-Петербург(Пулково)</StationName>
<TerminalName>1</TerminalName>
</Dep>
<Duration>PT1H45M</Duration>
<Distance UnitCode="Mileage">390</Distance>
<FranchiseCarrierInfo>
<CarrierDesigCode>FV</CarrierDesigCode>
<FranchiseCarrierFlightNumberText>6179</FranchiseCarrierFlightNumberText>
</FranchiseCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>SU</CarrierDesigCode>
<MarketingCarrierFlightNumberText>6179</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
<SegmentType>Aircraft</SegmentType>
<PaxSegmentID>39e35f1e-6eb6-4674-b581-56a15903d339</PaxSegmentID>
</PaxSegment>
Optionality of the ScheduledDateTime parameter¶
In the AirShoppingRS, OfferPriceRS, OrderViewRS, OrderReshopRS, AvailabilityRS, AirlineProfileRS, SeatAvailabilityRS и ServiceListRS response messages, the ScheduledDateTime parameter becomes optional:
The change is applied to the response message schema:
-
.../Response/DataLists/PaxSegmentList/PaxSegment/Arrival/ScheduledDateTime
-
.../Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/Arrival/ScheduledDateTime
-
.../Response/DataLists/PaxSegmentList/PaxSegment/DatedOperatingLeg/Dep/ScheduledDateTime
-
.../Response/DataLists/PaxSegmentList/PaxSegment/Dep/ScheduledDateTime
Base and applied fare codes¶
The base and applied fare codes are transmitted in the structure:
- .../FareDetail/FareComponent, in which:
.../FareComponent/FareBasisAppCode - applied fare code
.../FareComponent/FareBasisCode - base fare code
Remark Type¶
In the Mixvel_OrderCreateRQ and Mixvel_OrderChangeRQ methods, the Type parameter is filled only in uppercase in the structure:
- .../PaxSegmentRemarkList/PaxSegmentRemark/Type
An example of passing a remark in a request:
<PaxSegmentRemarkList>
<PaxSegmentRemark>
<OfferRefID>070d9e96-b59e-43c0-b00e-6d7feaaabe2e</OfferRefID>
<Type>OTHS</Type>
<Text>OTHER REMARK</Text>
</PaxSegmentRemark>
</PaxSegmentRemarkList>
Changes in Methods¶
Request for directions and schedules¶
Endpoint: /api/Order/AirlineProfile
Removing the TravelWithin element¶
In the AirlineProfileDataItem structure, the TravelWithin element is removed:
- Mixvel_AirlineProfile/Response/AirlineProfile/AirlineProfileDataItem/TravelWithin
Removing elements from the GeographicFilterCriteriaType array¶
The following elements are removed from the GeographicFilterCriteriaType structure:
-
Mixvel_AirlineProfile/Response/AirlineProfile/AirlineProfileDataItem/GeographicFilterCriteriaType/AreaCodeText
-
Mixvel_AirlineProfile/Response/AirlineProfile/AirlineProfileDataItem/GeographicFilterCriteriaType/CoordRadiusMeasure
-
Mixvel_AirlineProfile/Response/AirlineProfile/AirlineProfileDataItem/GeographicFilterCriteriaType/CountryCode
-
Mixvel_AirlineProfile/Response/AirlineProfile/AirlineProfileDataItem/GeographicFilterCriteriaType/CountrySubDivisionCode
-
Mixvel_AirlineProfile/Response/AirlineProfile/AirlineProfileDataItem/GeographicFilterCriteriaType/GeospatialLocation
Changing the Direction parameter¶
The Direction element becomes optional in the structure:
- Mixvel_AirlineProfile/Response/AirlineProfile/AirlineProfileDataItem/Direction
Subsequently, the element will be filled with the multi-leg flight flag.
Payment for an order/reservation¶
Endpoint: /api/Order/Change
Removing the SingleTicket parameter¶
The parameter for passing the flag about printing a ticket on one SingleTicket form is removed:
- Mixvel_OrderChangeRQ/Request/ResponseParameters/SingleTicket
This parameter is passed at the order creation stage (CreateOrderRQ); it does not need to be passed during payment due to element inheritance.
Seat map request¶
Endpoint: /api/Order/SeatAvailability
Changing the Offer array¶
In the SeatAvailabilityRQ request, the allowed number of occurrences of Offer elements has been changed in the structure:
- Mixvel_SeatAvailabilityRQ/Request/Offer
Now you can specify only one element.
Modifying the OfferItem and OrderItem arrays¶
In the OrderRulesRQ request, the allowed number of occurrences of OfferItem elements has been changed in the structure:
- Mixvel_OrderRulesRQ/Request/RulesCoreRequest/OfferRequest/OfferItem
In the OrderRulesRQ request, the allowed number of occurrences of OrderItem elements has been changed in the structure:
Mixvel_OrderRulesRQ/Request/RulesCoreRequest/OrderRequest/OrderItem
Only one occurrence of an element is allowed.
OrderViewRS message structure¶
Changing the display of VAT data¶
The Mixvel_OrderViewRS response removes the duplicate display of VAT data in the structure:
- Mixvel_OrderViewRS/Response/TicketDocInfo/FareDetail/FarePriceType/Price/TaxSummary/Tax
VAT information will now only be transmitted within the structure:
- Mixvel_OrderViewRS/Response/MixOrder/Order/OrderItem/FareDetail/Price/TaxSummary/Tax
Deleting the FareComponent structure¶
The structure containing information about the tariff component ceases to be filled:
- Mixvel_OrderViewRS/Response/TicketDocInfo/FareDetail/FareComponеnt
This information continues to be displayed in the structure:
- Mixvel_OrderViewRS/Response/MixOrder/Order/OrderItem/FareDetail/FareComponent
Requiredness of the OrderID element¶
In response messages, the OrderID parameter becomes mandatory:
- Mixvel_OrderViewRS/Response/TicketDocInfo/OrderRef/OrderID
Formation of a structure for insurance services¶
Starting with release 1.5.0, the procedure for generating a block for insurance services issued through SlTech has been changed:
- Mixvel_OrderViewRS/Response/TicketDocInfo
Previously, two blocks were created for a single insurance service: a separate document for the insurance policy and an itinerary receipt (IR) with EMD information. This setup resulted in data duplication, since the insurance service is a single item in the order, and both documents contained the same pricing information.
Now, a single block is generated for each insurance service, combining policy and EMD data. This eliminates duplication of information and aligns with the general MixVel logic: one insurance service (OrderItem) corresponds to one block.
Displaying the type of remark¶
The value of the Type parameter (remark type) is now converted to uppercase structure:
- Mixvel_OrderViewRS/Response/DataLists/RemarkList/Remark/Type
Example of display in structure:
<Remark>
<PaxSegmentRefID>4965a44f-388e-493a-aeab-6eff6d25ef56</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<RemarkID>1ceff375-eeac-435c-bc95-bb5437fca143</RemarkID>
<Type>OTHS</Type>
<Text>SSR REMARK</Text>
<StatusCode>HK</StatusCode>
<OrderRefID>82477-250912-OET6958</OrderRefID>
</Remark>
Removing the Remark structure from the MixOrder block¶
The following structure is removed from the OrderViewRS response messages:
- Mixvel_OrderViewRS/Response/MixOrder/Order/OrderItem/Remark
The information will be displayed only in the structure:
- Mixvel_OrderViewRS/Response/DataLists/RemarkList/Remark
The new structure is filled in starting with release 1.4.7.
Removing a Qty element¶
In the Mixvel_OrderViewRS response messages, the parameter for displaying the quantity of additional services <Qty> is removed from the structure:
- Mixvel_OrderViewRS/Response/DataLists/ServiceDefinitionList/ServiceDefinition/Qty
The parameter is transferred and will be displayed in the structure:
- Mixvel_OrderViewRS/Response/MixOrder/Order/OrderItem/Service/Qty
Order cancellation¶
Endpoint: /api/Order/Cancel
Transferring the OrderItemID parameter¶
In the OrderCancelRQ request, the OrderItemID parameter is removed:
- Mixvel_OrderCancelRQ/Request/MixOrder/Order/OrderItemID
To pass the OrderItemID element, the following structure will be used:
- Mixvel_OrderCancelRQ/Request/MixOrder/Order/OrderItem/OrderItemID
Example of the Mixvel_OrderCancelRQ request:
Show request example
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
<Header/>
<Body id="ID1">
<MessageInfo MessageId="703423d1-595c-49f5-98c2-5dcabe950276" TimeSent="2025-10-31T19:37:48Z"/>
<AppData>
<m:Mixvel_OrderCancelRQ xmlns:m="https://www.mixvel.com/API/XSD/Mixvel_OrderCancelRQ/1_01">
<Request>
<MixOrder>
<MixOrderID>96829-250124-MEO3189</MixOrderID>
<Order>
<OrderID>96829-250124-OEO3190</OrderID>
<OrderItem>
<OrderItemID>eb2ccbeb-9726-43f9-8cfb-b17291223c56</OrderItemID>
</OrderItem>
</Order>
</MixOrder>
</Request>
</m:Mixvel_OrderCancelRQ>
</AppData>
</Body>
</MixEnv:Envelope>
The new structure is now available at all stands.
Order/booking import¶
Endpoint: /api/Order/Import
Removing the ForceImport element¶
The <ForceImport> element is removed from the Mixvel_OrderImportRQ request. The functionality for updating order and passenger data, previously performed through the ForceImport parameter, has been moved to the Mixvel_OrderRetrieveRQ method.
- Mixvel_OrderImportRQ/Request/ExternalOrderRequest/ForceImport
To retrieve the current order status after changes in third-party systems, the Mixvel_OrderRetrieveRQ method is now used without additional parameters.
Return of a paid order Mixvel_OrderReshopRQ¶
Endpoint:/api/Order/Reshop
Changing the display of multi-coupon services in OrderReshopRS¶
When returning an order with two or more identical additional services (multi-coupon EMD) on different segments, the MixVel_OrderReshopRS response message for the entire order now displays a link to each individual PaxSegmentRefID segment in the array.
- MixVel_OrderReshopRS/Response/ReshopResults/ReshopOffers/Offer/AddOfferItem/ExistingOrderItem/PriceDifferential/DiffPrice/ServiceAssociations
Example of display:
<ExistingOrderItem>
<OrderItemRefID>5fb68b81-ba8e-40f6-bd96-32fc3de37880</OrderItemRefID>
<PriceDifferential>
<DiffPrice>
<ServiceAssociations>
<PaxSegmentRefID>cc4240a5-85f3-4c9f-bf1b-730a81e2704c</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<ServiceDefinitionRefID>3c199cf6-568b-4f9e-929c-02670bf65f45</ServiceDefinitionRefID>
</ServiceAssociations>
<ServiceAssociations>
<PaxSegmentRefID>fc240d0a-da06-4841-9b66-35e25f88b315</PaxSegmentRefID>
<PaxRefID>Pax-1</PaxRefID>
<ServiceDefinitionRefID>3c199cf6-568b-4f9e-929c-02670b34dcxsd</ServiceDefinitionRefID>
</ServiceAssociations>
<Price>
<TotalAmount CurCode="RUB">2598.00</TotalAmount>
</Price>
</DiffPrice>
</PriceDifferential>
</ExistingOrderItem>
Reserve seats¶
Endpoint: /api/Order/Inv-Guarantee
Deleting the InventoryGuaranteeID element¶
The InventoryGuaranteeID element is removed from the Mixvel_InvGuaranteeRS response:
- Mixvel_InvGuaranteeRS/Response/InventoryGuarantee/InventoryGuaranteeID
Previously, the element was of an informational nature and contained the preliminary seat reservation number.
MixVel Notification Service¶
Changing the Birthdate parameter¶
The display of the parameter in the Mixvel_OrderNotifRS response messages in the structure has been changed:
- Mixvel_OrderNotifRS/Response/Notifications/ChangeGroup/ChangeOperation/DocInfo/PaxInfo/Birthdate
Example of a parameter before release 1.5.0:
<Birthdate>1953-04-08T00:00:00+00:00</Birthdate>
Example of a parameter after release 1.5.0:
<Birthdate>1953-04-08</Birthdate>