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. Certain trains does not have seats reservation possible. According to Trainline rules the class of service is decoded in the following way: S-Standard not second , F-First, N - cannot be reserved. It is possible that other transport mode than standard "Train" can be returned, f.
Discount cards - for each passenger type, currently supported cards only for adults, when using discount cards combining different passenger types in one RailShopRS is forbiden, due to restrictions on BeNe side. The RailManageBooking service is used to create a new reservation booking for one or more journeys between specified locations, on specific dates, for a specific quantity and type of passengers or to carry out booking modification on a reservation that has not been paid.
Travelers — a collection of traveler names that are associated with the reservation, as well as their Contact information and frequent traveler cards. FareGroups — group of elements with tariff description — pricing details - preferably taken from RailShop response. Upon success, the output shows the reservation unique ID PNR locator and if available current state of reservation e.
RailManageBooking is a state-full service on Sabre side. Because of that Sabre session pooling is not allowed in all cases - meaning a single booking should be performed in a separate Sabre session that is created only for process of booking. Thanks to this RailManageBooking can be used in two modes:. Iterative mode — a workflow model allowing additional user input that is send in few requests linked by the same Sabre Session Token.
Request type orchestrate operations that can be performed by RailManageBooking service. By providing a list of RmbRequestType in request and appropriately managing sessions client can fine tune a booking process. Create - this operation creates a booking in vendor service in one shot - it is a shortcut for one-shot booking. It hides operations for each vendor in the background.
Update - used to initialize a workflow - usually used in modification of a booking or fine graining a booking process. Book - this operation is used for creating new booking used for SJ, instead of Create operation. Modification of a reservation is not possible for all vendors. In modification process the 'Operation' attribute is very important and is used in many different elements to define in the request which action should be taken on the given element.
Only sub—elements of the modified element that are given in the request are modified — and only them. If some of the sub-elements of the modified element are not given in the request but they existed in the element before the changes then after the changes those sub-elements remains unchanged in the updated element. If vendor to modify one element require to specify set of elements or group of elements than it is user responsibility to specify proper set or group of elements e.
If some of the sub-elements of the modified element are not given in the request but they existed in the element before the changes then after the changes those sub-elements are removed from the updated element. It is attribute that is translated to class code level in SNCF. This attribute was added as part of Souplesse Tarifaire functionality. For more details please refer to Handling time zones. Create a new booking - see Creating a booking in RZD.
Cancel an existing not confirmed not paid booking - see Cancelling a booking in RZD. Perform Check In operation - see Performing check in of a traveler during booking. In Russian Rail a booking is possible only for a single segment connection with maximal of 4 passengers. Below you can find a sample request to book a segment for 3 passengers 2 adults and an infant. Sabre provides a generic code mapping handling in some operations. Example can be a passenger code mapping. Russian Rail system allows to check-in a traveler for some trains.
The information if check-in is possible is passed in RailShop responses. In case of 'Schedule' it is passed in Details of a Segment. The check-in operation can be performed either during booking handled in RailManageBooking or as a separate process handled in RailManageTicket service.
Only one operation can be defined in each request. RailManageBooking Prebook is responsible for two things. First thing is a reservation place and second is a confirmation reserved places. Time limit between executing these operations is 5 minutes. After this time reservation will expire. RailManageBooking Book is responsible for purchase places. Time limit between purchase place and confirmation reserved places is 20 minutes. Passengers data should be unique. Group of elements first name, last name and email should be unique.
RailManageBooking Issue is responsible for purchase confirmation. Time limit between purchase places and purchase confirmation is 30 minutes. After this time all tickets will be voided. Itinerary - constains information about rail segments from, to, date, time etc. Keep in mind that this element does not respresents "Itinerary" in sense of SJ business unit. Below you will find information how "SJ Itinerary" is represented. FareGroups - constains references to sections Travelers and Itinerary in oder to specify what exactly should be booked.
Fares are prepared per each traveller for each group of segments - these segments should be grouped in exactly the same way as they were in RailShop response within Quotation element. It books one-way trip with one "SJ Itinereary" with one Segment from Stockholm to Goteborg for one traveler. This element describes outboud journey can contain many segments. If segments constains to many "SJ Itineraries" it will not be reflected here. Fare element should be created separetly for every traveler and for every "SJ Itinerary".
Fare element has exactly one reference to traveler. If there is more travelers or more itineraries in outbound journey here you should add more Fare elements. Below you can find example of structure of RailManageBooking for round trip and two passengers one "SJ Itinerary" for each direction. Esense of this example is a way how Fare elements are crated when there is two-direction trip with more than one passenger.
Esense of this example is fact that many Fare elements were created although there is only one passenger. Three segments. Base on this part of request it is not possible to group them into "SJ Itineraries". Fare for first "SJ Itinerary". Here it is possible to say that first "SJ Itinerary" has only one segment. Fare for second "SJ Itinerary". Here it is possible to say that second "SJ Itinerary" has two segments. In order to select ticket type set TicketType attribute inside each FareGroup element e. Traveler and contact data required name and surname. In addition it requires data related to ticket type.
For more info look into table above. Example snippet:. In addition references to passenger should include traveler type:. If you want specify you preferences related to seats you can add following elements to correct Segment elements inside Itinerary section. Even if there is more than one passenger you should specify maximum one Reservation element with exactseat number per segment.
SJ will try to find places for all passenger next to each other. In special cases like night trains RailShopRS. If you want to book any paid supplementary service you can add following elements inside Fare element. Keep in mind that if any free supplementary services are returned in RailShopRS you should create SupplementaryService elements also for them. Otherwise booking might be impossible. For some specyfic trains RailShopRS. In this case in order to book offer referencing to this fare you have to send RailShopRQ. AdditionalOptions and retrieve extended offers with full information.
This rule applies also to creation of RailShopRQ. Here you can specify which tickets should be canceled. In response there will be included complete information about reservation after changes. In order to book and issue ticket in one step you should send request similar to "BOOK". Only differences are that you should include two request types:. If in reservation there are many travelers but you want modify data only for one you can send only one Traveler element.
BOOK do not apply here. Trainline customer profiles reading and updating of contact information. See Contact. See MI Questions. All other elements are the same for both operations. RailManageBooking Issue is responsible for final purchase of tickets and reserve places. Selected offers can be extracted from RailShopRS. Every traveller should be referenced by exactly one QuotationItem. If the traveller has an Discount Rail Card , he should be assigned to QuotationItem with proper discount. Traveller without discount should be assigned to QuotationItem without any discount. Traveler Refs are required in the quotation items, each traveler must be assigned to exactly one quotation item.
Outbound journey only. For this type of journey, one OriginAndDestination, one matching Fare and one matching Offer elements required. Outbound and Inbound journey, each one on separate ticket. For this type of journey, two OriginAndDestinations, two matching Fare and Offer pairs one for outbound journey, one for inbound journey are required. Outbound and Inbound journeys on one ticket.
For this type of ticket, two OriginAndDestination and one matching Fare and Ticket pair of "Return" classification are required. Outbound and Inbound journeys on one ticket, but return journey is not specified yet. For this type of ticket, one OriginAndDestination and one matching Fare and Offer type of "Return" classification are required. NextDay — delivery mode may be rejected if train departs sooner than 1 [or2] working day for bookings made before [or after ]. Travelling Together - when only one passenger needs to show valid id specify one TravelerRef in Delivery Mode. If no Reservations element is found in every segment of the Journey, the default Trainline seat reservation rules apply.
Seat preferences have to be the same for every segment of a journey. That means that preferences can be provided only for the first Segment of the Journey, even if TransportMode is not "Train":. Another valid possibility is to specify the same Seat Preferences for every segment of the Journey:. During booking it is possible to pass MI Questions. On some Trainline configuration it may be mandatory to provide this answers. Answers are validated on Trainline side.
The "OnAccount" payment means that journey is being paid by a company that user profile belongs to. Payment with Credit Card requires credit card data to be passed including customer address, card number, expiry date and cvv2. Default RequestTypes are used with limitation that one operation can be defined in each request, except Book and Issue which can be combined together. Selected offers must be extracted from RailShopRS. All details and other data must be exactly the same.
The RailManageTicket service is used to issue tickets , cancel already issued tickets and send a confirmation email to the passengers with dematerialized tickets. Upon success, the response contains the representation of a SNCF PNR: itinerary, segments, remarks, traveler names, and additionally, the ticket information. Payment type e. PNR have 2 segments for 2 passengers.
Segment 1 was issued for passenger 1. There is no more possibility to issue all segments for passenger 1 or issue all segments for all passengers, only segment 2 can be issued for passengers 1 and segment 1 and 2 can be issued for passenger 2. Passengers names, date of birth, mobile phone number, email address, customer documents e. It should be used only in case of agent error and has a time restrictions - it needs to be done on the day of issuing PNR.
The IDs of the tickets affected by the immediate cancellation. The IDs of the passengers to whom a confirmation email must be sent. If no passenger is specified in input of the operation, the email will then be sent to all passengers. The operation sends back URL link to barcode generated. This operation requires a group booking performed as described in RailManageBooking service. It requires tickets to be Value paper ticket TKV. Managing check-in - after the booking has been confirmed an agent can manage the status of travelers. All bookings that have not been confirmed will be cancelled automatically after either 15 minutes or 3 hours - depending on actions taken by agent.
This value will be returned in [RailReservationRead service]. Paying for the reservation is performed with rmt:RequestType.
Philacanada - Timbres du Canada, valeur des timbres canadiens et erreurs et variétés
Pay element. This example includes passing AgencyFee to Sabre. A postponed booking must be either Confirmed or Cancelled. If neither of these steps occur the booking will be cancelled by Russian Rail. During a booking an agent can mark travelers as Checked-In see [Performing check in of a traveller during booking]. After the booking is confirmed the tickets stays in checked-in status. However if an agent does not mark tickets as check-in or wants to revoke Check-In status RailManageTicket service allows to do this. Check-in can be handled per whole booking all tickets and per ticket.
Detailed business cases when this operation is possible are described in UFS documentation and must be implemented. First request that must be sent is RMT. This request results in current statuses of tickets. The RailManageAfterSales service is used to deal with all operation after tickets were issued. The service is used to carry out after sales operation on a PNR that has been completely or partially issued. The following operations are available:. Refunding items e. To carry out these operations, except the return to availability, below workflow need to be followed up:.
Upon success, the output shows the PNR content PNR reference, passengers, segments etc and the after sales process status. The ReturnToAvailability operation is used to make seats available again without having to go through the initialization or finalization steps. After estimation step the only possibility is to finalize after sales process or cancel it by initiation of new after sale process. After sales workflow After sales operations in a sequence of calling for all possible after sales flows, except return to availability, are:.
All of those request types are allowed in one after sales process, however, not all combinations are allowed. Refund specific segments for specific passengers enter selected segments and selected passengers Refunding segments shall be used as a first modification step to exchange, next step is adding new items segments.
Operation used to add items segments to the existing PNR. However, this operation cannot be used to book new segments. It shall be used to exchange existing segments. After sales flow including this operation shall be: initiate, remove items segments , check availability, add items segments and validate. Operation used to change fares on existing segments, for all or some of the passengers, provided that the application conditions of the existing or modified fares are respected.
Change fares operation may:. Enter the type ticket to be issued in order to fix the taxation of the new elements or of the modified elements. Only one of those request types is allowed in one after sales process.
Les tarifs SNCF ont changé et c’est une bonne nouvelle
Enter the form of payment, the type of ticket to be issued and optionally regular or historical remarks. For ValidateNoPenalty request type, enter the reason code which justifies the elimination of penalties, if there was such elimination. The Validate step is not called and instead the Initiate step is called.
In such case all after sales modifications are canceled and the PNR is back to the state before the after sales process was started. The Initiate step can be called any time during the after sales process to cancel it. In this case all after sales modifications are canceled and the PNR is back to the state before the after sales process was started. Additionally this operation closes the connection. The service is used to carry out after sales operation on a PNR that has been completely issued.
Estimation of credit amount that need to be payed or will be returned to payer after exchange operation. Estimation does not change the status of any ticket. After successful refunding is performed, requested PNR become cancelled and the output shows the PNR content PNR reference, passengers, segments etc and the after sales process status. Successful performing of refund estimation provides information on amount of credit that will be returned to payer in form of return on credit card or return to e-voucher for refunding.
Successful performing of refund cancels requested tickets within reservation and prepares AMTRAK to return estimated money for refunded tickets to the payer. Required Payment attribute PaymentType set to Voucher if requested to return refund amount on e-voucher.
Perform refund on requested PNR. Successful performing of exchange estimation provides information about amount that need to be paid or returned to payer in form of return on credit card or return to e-voucher. RENFE supports refund tickets. Estimation of credit amount that will be returned to payer after refund refund all or some requested tickets of a PNR. After successful refunding is performed, requested tickets become cancelled and the output shows the PNR content PNR reference, passengers, segments etc and the after sales process status.
Successful performing of Estimation provides information on amount of credit that will be returned to payer for refunding requested tickets. Successful performing of Refund cancels requested tickets within reservation and prepares SJ to return estimated money for refunded tickets to the payer. After sales workflow After sales operations Estimation and Refunding operations can be called independently. For each user can provide data about specific tickets on which one of the two functionalities should be performed. Calculate refund amount for requested tickets or whole reservation if no tickets specified in request that will be returned to payer, should he perform refund.
Perform refund on requested tickets or on all remaining and valid for refund tickets if no particular tickets were specified in request. Upon success, requested tickets become cancelled and calculated refund amount for those tickets is returned to payer. Information about functionality that was performed with PaymentBalance info. For Refund functionality, no additional info is returned. Financial payment balance information concerning tickets on which upon action was performed. This consists of:. Total Charge containing data about sum of all tickets original amounts, sum of refund amounts and used currency.
Charges per each ticket on which functionality was performed upon containing original ticket amount, refund amount and currency. See Available Request Types. It is recommended to use the same request with only difference in RequestType. The "Estimate" Request Type is used to estimate the refundable amount and refund cost and cost of new tickets if exchange is being processed. Only tickets with "IsRefundable" flag set to "true" can be refunded. The reason of ticket being not refundable can be found under:.
Only tickets with "IsExchangeable" flag is set to "true" can be exchanged. The reason of ticket being not exchangeable can be found under:. In such case the refund will proceed with Trainline without any further action from the traveller or travel agent. The processing of refund after successful Refund operation may take a couple of minutes.
If traveller collected the ticket, e. In such case the printed tickets must be sent back to Trainline in order to complete the refund process and get the money back. VendorTicketStatus flag shows the current status of the reservation processed by Trainline already after successful webservice operation. Please be aware that requests are validated in Trainline at the moment of confirming operations. Examples of such validations:. Origin and destination have to be exactly the same as in the original booking for both direction of exchanged journey. The exchange process only applies to PYO tickets on special routes.
Refund or Exchange is available only after Trainline has finished processing. In typical case it should take approximately 15 minutes from the moment of booking. Returned when IsTicketPrinted flag set to true tickets printed or to be partially printed. Returned when IsTicketPrinted flag is set to false tickets not yet printed , Trainline will automatically validate and process the tickets. Required In order to process exchange one need to provide the segment to exchange to.
New segment element can be taken from RailShopRS as is. The service is used to retrieve vendor rail reservation. The reservation must exist in vendor system and user invoking services has to have access rights to this reservation. Upon success, the output shows the PNR content PNR reference, travelers, itinerary, fares, tickets, delivery modes, contacts etc.
In case of Amtrak PNR security - i. FareGroups - constains references to sections Travelers , Itinerary and Tickets in oder to described booked reservation. Tickets - contains information about tickets. Elements inside has references to travelers and segments. Every traveler receives separate ticket for every "SJ Itinerary". List of segments of outbound journey. Even if outbound joutney contains many "SJ Itineraries" all segments will be listed next to each other. Bese on this element it is imposible to determine which segment belogs to which "SJ Itinerary". There is Ticket for every FareGroup.
If there was any supplementary service booked you should expect like below inside correct Fare elements. If there was any seat booked you should expect like below inside correct Segment elements. If any discount was applied durring booking you should expect following element inside correct Fare elements. Tickets are presented the same way as in Trainline.
For regular Tickets, separate Ticket entity will be created for every passenger. In this special case two Delivery Mode entities will be returned, each with a reference to one journey:. To notify about this connection, additional Ticket relation will be returned:. Please note that some data or operation are fully available after finishing full processing on Trainline side, which usually takes no more than 15 minutes. Exchange capabilities - RailReservationRead before full Trainline processing will return that Ticket is not Exchangeable.
FareGroups - contains references to sections Travelers , Itinerary and Tickets in order to described booked reservation. Contact data is being returned if customer profile exists in Trainline. If not, no customer data is returned and warning that client does not exists is added to the response.
- Hotels travellers are raving about....
- chanel coupons 2019!
- Mens Clothing & Fashion - Shop Designer Menswear | Wrangler SE.
MI Questions are returned as supplementary data. Key parameters are:. SupplementaryDataLine Type - states if the questions is connected to ticket delivery "Delivery" or payment "Transaction".
- destiny taken king black friday deals.
- kohls coupons for handbags?
- TER Nord-Pas-de-Calais.
- bachelorette party deals in chicago!
- ikea uk coupon code free shipping.
If the Trainline customer profile per given corporation PCC has configured the TravelAgentAccount values they are returned in the payment sections and linked with particular payment methods. Those values must be used in the payment section in RailManageBooking request when selecting the particular payment method for given customer. The synchronization Web service is often used after updating the already existing booking , after ticketing , immediate cancellations or any after sales operations.
This Web service can be called at any time to ensure that both PNRs are synchronized. The Success element is also returned, otherwise a SOAP error is returned with the reason for failure. It is not synchronized if it differs. The RailLocation can be used to encode or decode stations. Encoding is an operation to retrieve station code based on station name. Decode is an operation to retrieve station name based on station code.
Fully or partially matching options can be returned. If no station exists within the provided location, other stations located nearby can be provided. Upon success, a list of stations is returned. Retrieve list of ticket offices. See List of Ticket Offices. Retrieve list of ticket machines.
See List of Ticket Machines. For Trainline it is possible to get list of stations equipped with ticket machines and ticket offices. This is a low level service used strictly for SNCF. In that respect, it is analogical to SabreCommand service that serves the same purpose but for Sabre Host commands. Not all commands are supported. Client needs to handle sessions on ResaRail side manually. Every time a new ResaRail session is opened it overrides an existing ResaRail session in cache.
The cancel request message RailCancelRQ performs a not paid booking cancellation on the Vendor system. Default behaviour - Success element is present or failure identified as list of Error elements. In addition, availability can be requested for a specific train, specific fare code or specific fare basis code - FBC by setting class of service and passenger types. A successful transaction returns train availability for a station pair on a specific date.
The response will comprise availability information and a list of all fares from the origin to the destination. A set of OriginDestinationOptions is returned, each of which contains one or more connecting trains that serve the city pair. Other availability in the response depends on the value of ResponseType in the request, as the preceding paragraphs describe.
Please see RailShop service. It is done by sending a CreateSessionRQ service providing three authorization parameters:. This value must be used in consequent calls to SWS. Each session has a time out value. By default it is set to 15 minutes. If no request is sent within 15 minutes the session will expire and all further requests will be rejected by SWS. Three most important elements are:. By providing a BinarySecurityToken client decides to close the session. Sabre PNR was already modified and changes made were not committed nor ignored. Unable to create Vendor PNR due to insufficient data in booking from the provider.
There was an attempt to retrieve Vendor PNR from Vendor service but provided PNR locator was different then the one that can be found in itinerary segments related to Vendor booking, or the locator form itinerary segments cannot be explicitly retrieved. At this point the active booking in SNCF was already cancelled.
Attempt to synchronize Sabre PNR that contains mergeback segments. They need to be removed first. The booking request has a different number of passengers than the Sabre PNR in the active session. Probably an error in client application. Synchronization to Sabre PNR is possible only when all passengers are assigned to all segments. This workflow step cannot be used in this state. Please refer to service documentation. Booking is still in Booked state not Issued and therefore cannot be refunded. There is an insufficient number of vacant seats available next to the already reserved seat to satisfy the "close to" placement wish.
Informations sur le voyage
The seat referred to by the "close to" wish does not exist or has not been reserved yet. Thus, the "close to" placement wish could not be satisfied. Please call AQ before calling RE. These calls have to be made within the same session. The identifier of at least one passenger does not correspond to its identifier in the quote request. The number of meal at seat wishes exceeds the number of passengers on the segment.
The placement wish expressed is not comprised in the placement options in the chosen segments. The special meal wish expressed is not comprised in the special meal options proposed for the segment. It is impossible to express more than one type of placement wish for the same travel segment. It is impossible to express a seat placement wish and a berth placement wish or a bed placement wish at the same time.
Please call EJ. The placement wish "Women Only" is impossible since there is at least one male passenger among the travellers. Il est impossible de souhaiter un placement "dame seule" car il y a au moins un homme parmi les passagers. The fares are incorrects or incompatibles with the input passengers. Please check your inputs. The PNR has been modified by another system and thus cannot be accessed anymore.
Journey removal impossible : the PNR must contain an outward and an inward journey. The PNR does not contain any travel segment it may have been cancelled , and thus cannot be accessed anymore. It is impossible to modify the name of one passenger twice in the same request. Only local queues can be considered for this operation. As such, the provided queue number must be between and Your demand requires more than one PNR split. QM is unable to process such request. This PNR has been issued globally. This operation cannot be performed.
Please issue it again individually. One of the fares is non refundable and non exchangeable. No quote is available. The number of seat placement cannot be superior to the number of passenger on the segment. The number of berth placement cannot be superior to the number of passenger on the segment. The number of bed placement cannot be superior to the number of passenger on the segment.
If you give electronic ticket retrieve card numbers, you must have choosen "Electronic Ticket" as ticket kind. Impossible to execute this operation with a PNR created before Notes. You have to cancel it and build a new one. NOTES est actif. There is not enough availability in the desired fare space - Please modify your demand. It is not possible to manage more than a handicapped traveller and a companion. A companion cannot beneficiate of a companion fare alone without any handicaped traveller. The name, first name and phone number must be specifed for the handicaped passenger in a wheelchair.
Only a blind passenger with a dog on a Corail Teoz train can ask for the blind contingent. Dedicated space is no more available for the handicapped traveller in a wheelchair. Ticketing global obligatoire, les options de tarifs, trajets choisis sont incompatibles. Electronic ticket not allowed, global ticketing mandatory for the given options.
Reservation is not possible on the whole trip for the handicaped passenger in wheelchair. Sabre Rail Web Services documentation v 1. Session pooling In some cases it is possible to reuse pool sessions in different request. In further parts of documentation Soap Envelope will be omitted not to clutter the samples. Handling time zones Dates and times provided in requests are treated as local time for provided stations. Both of them will be treated as the first one with omitted time zone :. Sabre Rail as a tool to generate requests which are always up-to-date This documentation contains a very limited number of samples.
RailReportsRQ Generates report gathering all operations for a specific period of time. SNCF Changelog for version 1. General description The availability request message RailShopRQ is used to return availability options and estimated prices for standard shopping, groups or subscription cards. Amtrak The availability request message RailShopRQ is used to return availability for travel classes as well as price estimation. Schedule - to retrieve availability on a given station pair and date Fares - to retrieve fares for a specific train.
Changelog No changes. RZD Schedule search request Schedule search is used to retrieve a list of trains operating between a given station pair on a given date. Origin and destination can be provided in form of: station name station code. RZD Schedule search response Response of RailShop consists of list of trains single segment only and basic fare information containing minimal and maximal price for each fare. Price - information regarding price in Rubles and payment status - immediate payment or deferred payment possible Details - provide RR specific information like allowed type of documents used in booking 'AllowedDocumentType' and 'ElectronicCheckIn'.
RZD fare search Fare search is used for queering for more detailed information about a given train. RZD fare search response Response of Fare search provides additional information only for a provided train. Seat map element provides information which seats are free in a given car. Popular on Groupon. Empire Corner Sofa Set. Crazy Boxer Surprise Pack. Resistance Loop Bands. Magnetic Posture Corrector. Skechers Memory Foam Shoes. Ever Youth Vitamin C Set. Charging and Syncing Cable.
Puma Toms Plimsolls. One page A4 hardback photobook. Tooky Toys My First Calendar. Replacement Strap for Fitbit. Inflatable Water Play Mat. Drain Cleaner Sticks. Victoria High Waist Swimsuit. Brush Microfibre Dust Cleaner. So Many Deals See Them All! Kappa Boxers Pack. Ruby Shoo Women's Heels.
Chiffon Midi Dress. Timothy Stone Norse Men's Watch. Finish Dishwasher Tablets.