RulesFromPrice (XML)
API情報
当該機能は、運賃ルールを表示するAPIです。本APIリクエスト前には、旅程作成と運賃計算が必要です。
詳細はワークフローをご確認ください。
Service Action Code | :RulesFromPriceLLSRQ |
最新バージョン | :2.1.0 |
プロトコル | :XML |
更新履歴
RulesFromPriceLLSRQ v2.1.0 on May 08, 2019
- Version2.1.0をリリースいたしました。
リクエストサンプル
Passenger TypeNumber1※の運賃、第1セグメント、運賃カテゴリー5,16を表示したい場合。 選択<RulesFromPriceRQ xmlns="http://webservices.sabre.com/sabreXML/2011/10" Version="2.1.0">
<RuleReqInfo>
<Category>5</Category>
<Category>16</Category>
<Passenger TypeNumber="1"/>
<SegmentSelect Number="1"/>
</RuleReqInfo>
</RulesFromPriceRQ>
レスポンスサンプル
選択<RulesFromPriceRS xmlns="http://webservices.sabre.com/sabreXML/2011/10" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:stl="http://services.sabre.com/STL/v01" Version="2.1.0">
<stl:ApplicationResults status="Complete">
<stl:Success timeStamp="2019-04-24T03:58:27-05:00"/>
</stl:ApplicationResults>
<FareRuleInfo>
<Header>
<Line Type="Legend">
<Text>V FARE BASIS AP FARE-OW FARE-RT BK SEASON MINMAX RTG</Text>
</Line>
<Line Type="Fare">
<Text>1 SRNS1 48000 S --- 2/ 2M EH01</Text>
</Line>
<Line Type="Passenger Type">
<Text>PASSENGER TYPE-ADT AUTO PRICE-YES</Text>
</Line>
<Line Type="Origin Destination">
<Text>FROM-TYO TO-SIN CXR-NH TVL-25JUL19 RULE-LA25 IPRPG/8</Text>
</Line>
<Line Type="Fare Basis">
<Text>FARE BASIS-SRNS1 SPECIAL FARE DIS-E VENDOR-ATP</Text>
</Line>
<Line Type="Fare Type">
<Text>FARE TYPE-XAP RT-REGULAR APEX</Text>
</Line>
<Line Type="Currency">
<Text>JPY 48000 3060 E01APR19 D-INFINITY FC-SRNS1 FN-4E</Text>
</Line>
<Line Type="System Dates">
<Text>SYSTEM DATES - CREATED 12MAR19/1022 EXPIRES INFINITY</Text>
</Line>
<ParsedData>
<CurrencyLine>
<Amount>48000</Amount>
<CurrencyCode>JPY</CurrencyCode>
<Discontinue>INFINITY</Discontinue>
<Effective>2019-04-01</Effective>
<FareClass>SRNS1</FareClass>
<RoutingNumberOrMPM>3060</RoutingNumberOrMPM>
<TariffDescriptionNumber>4E</TariffDescriptionNumber>
</CurrencyLine>
<FareBasisLine>
<DisplayType Code="E"/>
<FareBasis Code="SRNS1"/>
<FareVendor>ATP</FareVendor>
<Text>SPECIAL FARE</Text>
</FareBasisLine>
<FareTypeLine>
<FareDescription Code="RT">REGULAR APEX</FareDescription>
<FareType>XAP</FareType>
</FareTypeLine>
<OriginDestinationLine>
<Airline Code="NH"/>
<DestinationLocation LocationCode="SIN"/>
<OriginLocation LocationCode="TYO"/>
<Rule>LA25</Rule>
<TariffDescriptionNumber>IPRPG/8</TariffDescriptionNumber>
<TravelDate>2019-07-25</TravelDate>
</OriginDestinationLine>
<PassengerTypeLine>
<AutoPrice>YES</AutoPrice>
<PassengerType Code="ADT"/>
</PassengerTypeLine>
<SystemDatesLine>
<CreateDateTime>2019-03-12T10:22</CreateDateTime>
<ExpireDateTime>INFINITY</ExpireDateTime>
</SystemDatesLine>
</ParsedData>
</Header>
<Rules>
<Paragraph RPH="05" Title="ADVANCE RESERVATIONS/TICKETING">
<Text>IF TRAVEL COMMENCES DEPARTURE OF FIRST INTERNATIONAL
SECTOR ON/AFTER 20SEP18 AND ON/BEFORE 31MAR19.
CONFIRMED RESERVATIONS FOR ALL SECTORS ARE REQUIRED
AT LEAST 5 DAYS BEFORE DEPARTURE OF FIRST
INTERNATIONAL SECTOR.
WAITLIST NOT PERMITTED.
WHEN RESERVATIONS ARE MADE AT LEAST 29 DAYS BEFORE
DEPARTURE, TICKETING MUST BE COMPLETED WITHIN 7 DAYS
AFTER RESERVATIONS ARE MADE.
OR - CONFIRMED RESERVATIONS FOR ALL SECTORS ARE
REQUIRED AT LEAST 5 DAYS BEFORE DEPARTURE OF
FIRST INTERNATIONAL SECTOR.
WAITLIST NOT PERMITTED.
TICKETING DEPARTURE OF FIRST INTERNATIONAL
SECTOR MUST BE COMPLETED WITHIN 3 DAYS AFTER
RESERVATIONS ARE MADE OR AT LEAST 5 DAYS BEFORE
DEPARTURE WHICHEVER IS EARLIER.
NOTE - TEXT BELOW NOT VALIDATED FOR AUTOPRICING.
RESERVATIONS MAY BE CANCELLED AUTOMATICALLY
ON TLC DATE NO MATTER THE STATUS IS.
----------------------------------------------
DUE TO AUTOMATED TICKETING DEADLINE CONTROL
DIFFERENCE COULD EXIST BETWEEN THE FARE RULE
LAST TICKETING DATE AND THE SYSTEM GENERATED
TICKETING DEADLINE MESSAGE.
THE MORE RESTRICTIVE TICKETING DEADLINE APPLIES.
IF TRAVEL COMMENCES DEPARTURE OF FIRST INTERNATIONAL
SECTOR ON/AFTER 01APR19.
CONFIRMED RESERVATIONS FOR ALL SECTORS ARE REQUIRED
AT LEAST 5 DAYS BEFORE DEPARTURE FROM FARE ORIGIN.
WAITLIST NOT PERMITTED.
WHEN RESERVATIONS ARE MADE AT LEAST 29 DAYS BEFORE
DEPARTURE, TICKETING MUST BE COMPLETED WITHIN 7 DAYS
AFTER RESERVATIONS ARE MADE.
OR - CONFIRMED RESERVATIONS FOR ALL SECTORS ARE
REQUIRED AT LEAST 5 DAYS BEFORE DEPARTURE FROM
FARE ORIGIN.
WAITLIST NOT PERMITTED.
TICKETING DEPARTURE FROM FARE ORIGIN MUST BE
COMPLETED WITHIN 72 HOURS AFTER RESERVATIONS ARE
MADE OR AT LEAST 5 DAYS BEFORE DEPARTURE
WHICHEVER IS EARLIER.
NOTE - TEXT BELOW NOT VALIDATED FOR AUTOPRICING.
RESERVATIONS MAY BE CANCELLED AUTOMATICALLY
ON TLC DATE NO MATTER THE STATUS IS.
----------------------------------------------
DUE TO AUTOMATED TICKETING DEADLINE CONTROL
DIFFERENCE COULD EXIST BETWEEN THE FARE RULE
LAST TICKETING DATE AND THE SYSTEM GENERATED
TICKETING DEADLINE MESSAGE.
THE MORE RESTRICTIVE TICKETING DEADLINE APPLIES.</Text>
</Paragraph>
<Paragraph RPH="16" Title="PENALTIES">
<Text>CANCELLATIONS
BEFORE DEPARTURE
CHARGE JPY 20000 FOR CANCEL/NO-SHOW/REFUND.
NOTE - TEXT BELOW NOT VALIDATED FOR AUTOPRICING.
CHILD DISCOUNT APPLIES.
INFANT WITHOUT SEAT FREE OF CHARGE.
---------------------------------------
CANCELLATION RULES APPLY PER PRICING UNIT.
WHEN COMBINING FARES THE MOST RESTRICTIVE
CANCELLATION CONDITIONS APPLY FOR THE ENTIRE
PRICING UNIT.
---------------------------------------
SEE THE PAGE BOTTOM FOR WAIVER POLICY
AFTER DEPARTURE
TICKET IS NON-REFUNDABLE.
NOTE - TEXT BELOW NOT VALIDATED FOR AUTOPRICING.
CANCELLATION RULES APPLY PER PRICING UNIT.
WHEN COMBINING FARES THE MOST RESTRICTIVE
CANCELLATION CONDITIONS APPLY FOR THE ENTIRE
PRICING UNIT.
---------------------------------------
SEE THE PAGE BOTTOM FOR WAIVER POLICY
CHANGES
ANY TIME
CHANGES NOT PERMITTED.
NOTE - TEXT BELOW NOT VALIDATED FOR AUTOPRICING.
CHANGE RULES APPLY PER FARE COMPONENT
/DIRECTION.
------------------------------------------
SEE THE PAGE BOTTOM FOR WAIVER POLICY
NOTE - TEXT BELOW NOT VALIDATED FOR AUTOPRICING.
1 WAIVER POLICY FOR CANCELLATIONS
- WAIVED FOR ILLNESS/INJURY OF PASSENGER OR
ACCOMPANYING PASSENGER.
- WAIVED FOR DEATH OF PASSENGER/ACCOMPANYING
PASSENGER OR IMMEDIATE FAMILY MEMBER NOT
TRAVELING TOGETHER.
- WAIVER FOR ILLNESS/INJURY OR DEATH MUST BE
SUBSTANTIATED BY A VALID MEDICAL OR DEATH
CERTIFICATE.
-----------------------------------------
2 WAIVER POLICY FOR CHANGES
FOLLOWING POLICY APPLIES AFTER DEPARTURE ONLY
- IN CASE OF ILLNESS/INJURY OF PASSENGER OR
ACCOMPANYING PASSENGER DATE CHANGE OR REROUTING
USING ORIGINAL CARRIER/TO THE POINT OF ORIGIN
SHOWN ON THE TICKET IS PERMITTED WITHOUT PENALTY
OR ADC.
- IN CASE OF DEATH OF PASSENGER/ACCOMPANYING
PASSENGER OR IMMEDIATE FAMILY MEMBER NOT
TRAVELING TOGETHER DATE CHANGE OR REROUTING USING
ORIGINAL CARRIER/TO THE POINT OF ORIGIN SHOWN ON
THE TICKET IS PERMITTED WITHOUT PENALTY OR ADC.
- WAIVER FOR ILLNESS/INJURY OR DEATH MUST BE
SUBSTANTITATED BY A VALID MEDICAL OR DEATH
CERTIFICATE.</Text>
</Paragraph>
</Rules>
</FareRuleInfo>
</RulesFromPriceRS>
XMLタグ定義書
-
- リクエスト (2019/05/08更新)
-
- レスポンス (2019/05/08更新)
XMLスキーマ
【注意点】
各種XMLスキーマは、Sabre社提供のオリジナル版となるため、「XMLタグ定義書」の記載上、
利用不可の情報が含まれております。
スキーマを利用してアプリケーションを構築される場合の各タグの利用可否は、
必ず「XMLタグ定義書」にてご確認ください。
※弊社にて「XMLタグ定義書」を作成する際、各タグの利用可否確認を行っております。
各種XMLスキーマは、Sabre社提供のオリジナル版となるため、「XMLタグ定義書」の記載上、
利用不可の情報が含まれております。
スキーマを利用してアプリケーションを構築される場合の各タグの利用可否は、
必ず「XMLタグ定義書」にてご確認ください。
※弊社にて「XMLタグ定義書」を作成する際、各タグの利用可否確認を行っております。
-
- リクエストスキーマ
-
- レスポンススキーマ