Version - specifies schema version - this documentation describes 1. TargetSystem - defines which vendor this requests targets. PrimaryLangID - defines a language in which a response will be provided. Not all vendors support all possible languages.

Author:Aralabar Tojale
Country:Puerto Rico
Language:English (Spanish)
Published (Last):3 August 2015
PDF File Size:11.59 Mb
ePub File Size:2.71 Mb
Price:Free* [*Free Regsitration Required]

Version - specifies schema version - this documentation describes 1. TargetSystem - defines which vendor this requests targets. PrimaryLangID - defines a language in which a response will be provided.

Not all vendors support all possible languages. CorrelationID - this value is a randomly generated value helpful in tracing traffic from customers. In some cases it is possible to reuse pool sessions in different request. If session pooling will be used it is imperative to use it only with services that clearly state that it is possible. Not complying with this rule may result in serious business errors.

Dates and times provided in requests are treated as local time for provided stations. Any other usage, i. This applies to all services for every vendor with exception to Russial Rail, where time zones can be important. For more information please refer here: RZD. This documentation contains a very limited number of samples. You can generate real traffic for use cases you are interested in with our Sabre Rail application. If the app is not available please contact Support Team RailActivations sabre.

To enable traffic logging you need to add following line at the end of the file to mysabre. Requests and responses will be logged in in SRW log file look for edge.

Documentation of business processes with use of Sabre Rail can be found on Agency Services site use Sabre credentials to log in e. NOTE: this service is deprecated and returns only offers for French market.

Please use RailShopRQ instead. It is used to pass number of passengers that will travel in a booking that is being created. It was added as a part of Souplesse Tarifaire functionality. It is class code level. It is used to display real time information about journey. It is used to display real time information about segment. The availability request message RailShopRQ is used to return availability options and estimated prices for standard shopping, groups or subscription cards.

For more details please refer here: Handling time zones. The availability request message RailShopRQ is used to return availability for travel classes as well as price estimation. Response will contain Journeys for the specified connection with offered services or prices. Additionally add ancillary services and passenger cards. Response will contain Journey with detailed pricing per each traveler. Schedule search is used to retrieve a list of trains operating between a given station pair on a given date.

Searching for trains is available on routes domestic to Russia Federation and from to Russia and neighbouring countries Finland, Poland, Ukraine, Belarus and former Soviet Union countries. Response of RailShop consists of list of trains single segment only and basic fare information containing minimal and maximal price for each fare. Segment - detailed information regarding this specific segment - The most important is TrainNumber attribute used in [RR Fare search]. Additionally generic information regarding availability for a given class of service is present.

AvailabilityDetail in Segment - this element provides information regarding class of service ClassCode and data about accommodation Accommodations. ClassCode - represents information regarding class of service - including code e.

Accommodations - in this response represents general information regarding free places in train for given class of service. In Schedule search for each fare in segment there are only up to two offers available marking lowest and highest prices. Price - information regarding price in Rubles and payment status - immediate payment or deferred payment possible.

Fare search is used for queering for more detailed information about a given train. Specifies a number of a train to get details for. Can be acquired from response of Shedule search. Response of Fare search provides additional information only for a provided train. The response may contain more offers for given segment. PaymentsBalance elements provide information about an UFS account balance assigned for given agency. In RailShopRS we get information about availability.

If availability is equal , it means that in this offer is available more than 10 places. The RailShopRQ message is used to acquire schedules, availability options estimated journey prices, supplementary services options and seat options. Offer elements inside Offers section contains information about prices, availability, passenger types etc. Every Offer has one reference to Fare element in Fares section. In Fare you can find information about comfort standard of higher and flexibility rebookable, refundable etc of offer.

In OriginAndDestinationOption you can find information about segements of journey city names, dates, times, train type etc. In other words Offer provides price for traveling in some specyfic journey described in OriginAndDestination section with some specyfic rules described in Fares section.

Segment is a basic unit of travel and represents one train traveling between two stations. SJ groups rail segments into so called "Itineraries". This buissiness structure is represnted by elements Quotation inside Offer. Offer can contain one or many Quotation elements. Every Quotation element has references one or many to Segment elements. Below you can find simplified RailShopRS. It represents reponse with only one offer for train from Stockholm to Uppsala.

Price for non-rebookable ticket in standard level of comfort is SEK. Below you can find simplified example with round trip. When you request information about travel in both directions you should expect separate Offer elements for each direction. Additionally response contain two OriginAndDestination elements. Keep in mind that segment IDs are unique across whole response. This rule does not apply to quoation IDs. Quotation elements inside every Offer have IDs starting from 1. Below you can find simple example of offer for multi-itinerary journey.

Key difference is that in this case you can find many Quotation elements inside one Offer. This mode is used to retrieve a list of all journey options for specified parameters. Only schedule is returned, without offer prices.

If you want to request for round trip information here you should insert next AvailQueryCriteria element. Apart from schedule, offer prices are returned. Response will contain max 10 offers.

This mode is used to retrieve ancillary services for a specific journey. Request may contain a one-way journey or a round-trip selected from response of RailShop 'Fare' request. Response contains list of possible supplementary services for each itinerary. If you want to request for round trip information here you should add next AvailQueryCriteria element. Fare elements in this requst groups segments from one Itinerary.

Key detail of this response is element SupplementaryServices inside Offer. If supplementary service does not contain reference to segments in means it is available in all segments of given quotation. This mode is used to retrieve detailed pricing and seating options with prices for a specific journey.

Response contains list of seat prices for each passengers for each itinerary and sum of seat prices per itinerary. There are three key details of this response:. Details with booking rule inside Segment element in OriginAndDestination section.

SupplementaryServices element inside Offer element in Offers section. Segement ID returned in response matches segment ID in request even if it does not starts from 1. Both Return and Each Way separate single ticket for both directions offers will be returned if available.

It is possible to search for fares using Rail Cards. This can be achieved by using Discounts element in AvailQueryCriteria.

The total number of different cards is 3. The sum of Rail Cards' quantities must be no bigger than number of passengers. Set this to 1 to search for direct trains only. Max connections filter is taken only from the first AvailQueryCriteria and applied for the whole request. Possible values for available offers are:. NR - offer available - optional seat reservation seats reservation is available or not and could be reserved on request upon of Train Operator seats availability.

SA - offer available - required seat reservation seats reservation is available and must be reserved.


EUR-Lex Access to European Union law

Denis, France,represented by Cabinet Santarelli, France. On January 10, , the Center transmitted by email to the Registrar a request for registrar verification in connection with the disputed domain name. On the same date, the Registrar transmitted by email to the Center its verification response confirming that the Respondent is listed as the registrant and providing the contact details. The Panel finds that it was properly constituted. The Panel has submitted the Statement of Acceptance and Declaration of Impartiality and Independence, as required by the Center to ensure compliance with the Rules, paragraph 7. Consequently, the Panel ordered the Center to re-notify the Complaint and annexes to the Respondent to all the available e-mail addresses, including the one missed in the original Notification of Complaint. On the same day, the Center made the necessary re-notification in accordance with the Procedural Order.


Sabre Rail Web Services documentation v 1.12.0



File:N Scale - SNCF 141 P Mikado, 2-8-2 - France - IMG 0032.jpg


Related Articles