Checking segment consistency¶

General terms¶

Endpoint: /api/Order/Route-Check-Consistency

To check the consistency of segments in a booking by departure/arrival time and connecting point, the Mixvel_RouteCheckConsistencyRQ query is used. A consistency check may be required when processing schedule changes. Method allows to identify potential segment inconsistencies and ensure route integrity.

Request structure¶

The request input data must satisfy the scheme Mixvel_RouteCheckConsistencyRQ.xsd and contain the following basic data (the table shows the main parameters of the message, complete parameters can be found in the xsd diagram or in the xml examples of a specific message):

Parameter XPath	Filling example	Description
Mixvel_RouteCheckConsistencyRQ/Request/MixOrder/MixOrderID	96829-250325-MEH1234	Unique ID of the shopping cart
Mixvel_RouteCheckConsistencyRQ/Request/MixOrder/Order/OrderID	96829-250325-OEH1235	Unique ID of the order (optional)

Response structure¶

The system response to a checking segment consistency request corresponds to the scheme Mixvel_RouteCheckConsistencyRS.xsd and contains the following basic data (the table shows the main parameters of the message, complete parameters can be found in the xsd schema or xml examples of a specific message):

Parameter XPath	Filling example	Description
Mixvel_RouteCheckConsistencyRS/Response/MixOrder/MixOrderID	96829-250325-MEH1234	Unique ID of the shopping cart
Mixvel_RouteCheckConsistencyRS/Response/MixOrder/Order/BadPaxSegmentRoute	complex	A structure describing inconsistent segments. The InconsistentCount attribute specifies the number of inconsistent segments. If there are no such segments, the attribute specifies the value 0
Mixvel_RouteCheckConsistencyRS/Response/MixOrder/Order/BadPaxSegmentRoute/Reason	SEGMENT 1 does not connect with the previous one in terms of time	Description of the reason for the inconsistency of segments
Mixvel_RouteCheckConsistencyRS/Response/MixOrder/Order/OrderID	96829-250325-OEH1235	Unique ID of the order

Example of Mixvel_RouteCheckConsistencyRQ:

Show the request example

<MixEnv:Envelop xmlns:MixEnv="http://www.mixvel.com/API/XSD/mixvel_envelope/1_04">
    <Header/>
    <Body id="ID1">
        <MessageInfo MessageId="703423d1-595c-49f5-98c2-5dcabe950276" TimeSent="2025-03-27T18:56:39Z"/>
        <AppData>
            <m:Mixvel_RouteCheckConsistencyRQ xmlns:m="https://www.mixvel.com/API/XSD/Mixvel_RouteCheckConsistencyRQ/1_00">
                <Request>
                    <MixOrder>
                        <MixOrderID>96829-250325-MEH5881</MixOrderID>
                        <Order>
                            <OrderID>96829-250325-OEH5882</OrderID> <!--Order ID (optional)-->
                        </Order>
                    </MixOrder>
                </Request>
            </m:Mixvel_RouteCheckConsistencyRQ>
        </AppData>
    </Body>
</MixEnv:Envelop>

Example of Mixvel_RouteCheckConsistencyRS:

Show the response example

<?xml version="1.0" encoding="utf-8"?>
<MixEnv:Envelope xmlns:MixEnv="https://www.mixvel.com/API/XSD/mixvel_envelope/1_06">
    <Header />
    <Body>
        <MessageInfo MessageId="e997e9be-62e8-484e-a513-8209cf4d9672" ReplyTo="703423d1-595c-49f5-98c2-5dcabe950276" TimeSent="2025-03-27T18:56:39.237676Z" />
        <AppData>
            <Mixvel_RouteCheckConsistencyRS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="https://www.mixvel.com/API/XSD/Mixvel_RouteCheckConsistencyRS/1_01">
                <Response xmlns="">
                    <MixOrder>
                        <MixOrderID>96829-250325-MEH5881</MixOrderID>
                        <Order>
                            <BadPaxSegmentRoute InconsistentCount="0" />
                            <OrderID>96829-250325-OEH5882</OrderID>
                        </Order>
                    </MixOrder>
                </Response>
            </Mixvel_RouteCheckConsistencyRS>
        </AppData>
    </Body>
</MixEnv:Envelope>